-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cargo update --breaking
doesn't respect pre release
#14178
Comments
I don't think Cargo allows upgrade pre-release versions at this moment. You may need to specify each crate separately with the That said, maybe at this moment before figuring out the correct SemVer for pre-releases, cc @torhovland |
Yes, it looks like we should not try to upgrade (or downgrade) dependencies that are currently on a pre-release. Except maybe if there is a proper release that is higher than the current pre? @epage Thoughts? I will be away for a few weeks now, so if anybody wants to tackle this, feel free. Nice to see that we are faster than |
Yes,
|
Also, being faster is easy; cargo-edit does not use the sparse registry. |
added to #12425 (comment). |
If no one on this, I will take a look |
cargo update --breaking
doesn't respect pre release
Problem
Hello!
I use
cargo update
fromnightly
release to upgrade dependenciesHowever looks like
cargo
doesn't respect beta semver:Notice the line
Upgrading tauri ^2.0.0-beta.21 -> ^1.7.0
Steps
Then compare with https://crates.io/crates/tauri/versions
Possible Solution(s)
Respect beta versions
Notes
Also, I wanted to say that I'm really looking forward to seeing this feature, as I'm using cargo upgrade from
cargo-edit
, which takes tremendous time to upgrade dependencies, while cargo update from nightly does the same job much quicker.Version
The text was updated successfully, but these errors were encountered: