Support ~ and = operators in version specification #402
Conversation
This file contains hidden or 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
…dling instead of panicking
|
Following this the only unsupported operator (that's supported by Cargo) is |
|
We could potentially yank v0.15.0. People who are on it already are probably updating fairly frequently. But it would probably still be good to give it some time to bake after cutting another release before we actually tried to use these. |
tarcieri
approved these changes
Jul 9, 2021
That was the case until yesterday, when we broke v0.12 users 😝 Presumably they're all on v0.15 now |
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.
~operator in version requirements, add tests=operator in version requirements, add tests^operator handling spec-compliant, add tests. The spec discrepancy doesn't seem to affect the current DB data.After this is merged, if we use
~requirements in the DB, that will work on both very old cargo-audit versions and very new ones, but version 0.15.0 exactly will be broken (it's the only released version with rustsec v0.24 before these changes)