fix(cargo): set default rangeStrategy to 'bump' #4751
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
* It fixes unexpected "downgrading" behavior when updating normal versions like `0.9.21`, which are treated as caret ranges by cargo. For example if rangeStrategy is 'replace', an update like `0.9.21` -> `0.9.22` will result in newValue = `0.9.0`, because "caret range" `0.9.0` contains both `=0.9.21` and `=0.9.22`
|
Sounds like our “replace” strategy is flawed though? |
rarkins
changed the title
|
🎉 This PR is included in version 19.65.9 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Change cargo manager's default
rangeStrategytobump.It fixes unexpected "downgrading" behavior when updating normal versions like
0.9.21, which are treated as caret ranges by cargo.For example if rangeStrategy is 'replace', an update like
0.9.21->0.9.22will result in newValue =0.9.0, because "caret range"0.9.0contains both=0.9.21and=0.9.22.Tested with an example crate on gitlab.
Closes #4620