Respect lockfile except when necessary to work around old cargo bugs #242
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
taiki-e
added
the
A-version
taiki-e
force-pushed
the
generate-lockfile
branch
2 times, most recently
from
3be9907
to
c8e6133
Compare
taiki-e
force-pushed
the
generate-lockfile
branch
from
c8e6133
to
cd552a7
Compare
|
Published in 0.6.24. |
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.
For now, I think this is a reasonable compromise to progress #234 without breaking existing workflows such as what is mentioned in rust-lang/cargo#13523 (comment).
See #234 (comment) for more information.
Changes:
Cargo.lockwith--version-range/--rust-versionexcept when necessary to work around old cargo bugs.If you want to ensure that the existing
Cargo.lockis respected in all cases, please use--locked.FYI @epage