-
-
Notifications
You must be signed in to change notification settings - Fork 9
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
Switch to using cargo-edit
for cargo upgrade
command
#61
Conversation
Ran this locally to test (had to comment out cargo changes
npins changes
|
Man, I don't know. semver is just someone's opinion in practice. I kind of prefer the "update and see if it builds and tests" approach we have today. |
The `cargo update` command updates the version of the dependency in the `Cargo.lock` file based on the semver compatibility specified in the `Cargo.toml` file. It will not change the version range specified in the `Cargo.toml` file.
I didn't notice that I had to add I can't tell if that's what you meant or if you thought I was changing it to respect semver. Currently |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I did some research. I think this works.
Note that CI also runs the update command for you: https://github.com/NixOS/nixpkgs-check-by-name/actions/runs/8976276467#summary-24652778846 😉 Looking good to me btw, thanks for taking care of this! |
The current
cargo update
command updates the version of dependencies in theCargo.lock
file based on the semver compatibility. It will not change the version range specified in theCargo.toml
file.