Use un-released fix to semver-parser #731
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
semver 0.11.0 changed the behaviour of parsing `x.y` requirements - in semver 0.10 it treated them as `>=x.y.0, <(x+1).0.0` and in semver 0.11 it treated them as `>=x.y.0, <x.(y+1).0`. `cargo` itself is still using semver 0.10.0, but `cargo_metadata` and `cargo-lock` have updated to semver 0.11.0, which means that `cargo` and `crate_universe` currently treat these version ranges differently. This patch restores the `semver 0.10.0` behaviour, which means that `cargo` and `crate_universe` will resolve things the same.
UebelAndre
approved these changes
May 10, 2021
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.
semver 0.11.0 changed the behaviour of parsing
x.yrequirements - insemver 0.10 it treated them as
>=x.y.0, <(x+1).0.0and in semver 0.11it treated them as
>=x.y.0, <x.(y+1).0.cargoitself is still using semver 0.10.0, butcargo_metadataandcargo-lockhave updated to semver 0.11.0, which means thatcargoandcrate_universecurrently treat these version ranges differently.This patch restores the
semver 0.10.0behaviour, which means thatcargoandcrate_universewill resolve things the same.