-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Use cargo fetch for updating lock files #29620
Labels
manager:cargo
Cargo/Rust/crates.io
priority-3-medium
Default priority, "should be done" but isn't prioritised ahead of others
type:feature
Feature (new functionality)
Comments
rarkins
added
type:feature
Feature (new functionality)
priority-3-medium
Default priority, "should be done" but isn't prioritised ahead of others
manager:cargo
Cargo/Rust/crates.io
labels
Jun 12, 2024
1 task
6 tasks
🎉 This issue has been resolved in version 38.42.0 🎉 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.
Labels
manager:cargo
Cargo/Rust/crates.io
priority-3-medium
Default priority, "should be done" but isn't prioritised ahead of others
type:feature
Feature (new functionality)
Describe the proposed change(s).
Discussed in #29539
Per https://doc.rust-lang.org/cargo/commands/cargo-fetch.html, "cargo fetch" will update a lock file to match the Cargo.toml
This command would be better to use than our existing
cargo update
one. I think we can adopt this algorithm:cargo fetch
cargo update
targeting only those dependencies (similar to today)We might need an additional
cargo fetch
after thecargo update
commands, but we can leave that out for now if we're not sure.The text was updated successfully, but these errors were encountered: