A method to update manifest version requirements (like cargo-edit's `cargo-upgrade`)

[Milo123459]

Problem

I had a crate that was defined in my projects Cargo.toml, it updated the version in the Cargo.lock, but not the Cargo.toml

Proposed Solution

It would be cool if cargo update also updated Cargo.toml if applicable.

Notes

No response

[epage]

I do not know if there is a dedicated issue for this but I plan to follow up on the cargo-add issue by merging other cargo-edit subcommands, like cargo-rm and cargo-upgrade.

cargo-upgrade is probably the least defined for what it will look like merged with questions like

• Should it be a separate command or a flag on cargo-update?
• Should --skip-compatible be a default? the only behavior?

Something that someone can do to help is to scour other language packaging tools for existing precedence in how they handle cases like this like the cargo-add PR does.

[epage]

Hmm, this issue is more about cargo update updating both files at once which is a subset of cargo upgrades behavior and might be part of the subset we don't merge immediately, so this probably isn't the best issue for tracking the cargo-upgrade integration

[epage]

#12425 was created specifically for incompatible version upgrades.

The FCPed proposal intentionally left this use case out

Somewhere between deferred and rejected (speaking for myself): Support in cargo update for writing to the manifest for non-breaking changes, like bulk compatible upgrades of version requirements (ie a -save flag) which was one of our lower priority workflows. A --save flag is more about updating versions for your dependents, which while important for having valid lower-bounds on version requirements, doesn't fit with the existing model of cargo update. Maybe in the future we can find a way to express this in cargo update that fits with how it works or maybe another command can take on this role. We just aren't wanting to distract our efforts for handling most of the use cases to handle this one.

See also https://internals.rust-lang.org/t/feedback-on-cargo-upgrade-to-prepare-it-for-merging/17101