fix(upgrade): --to-lockfile changes all sources
#736
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
With path and git dependencies, you can specify a version for use with the registry. If its incompatible, I believe the resolver will fail, so we don't need to handle that case. That just leaves `--to-lockfile`. This just means post-poning the check for the registry to be in the non-lockfile case. Fixes killercup#426
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With path and git dependencies, you can specify a version for use with
the registry. If its incompatible, I believe the resolver will fail, so
we don't need to handle that case. That just leaves
--to-lockfile.This just means post-poning the check for the registry to be in the
non-lockfile case.
Fixes #426