cargo add clap@4.1.3
lock to the version specific
#11687
Labels
C-feature-request
Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`
Command-add
Problem
If I'm explicitly setting the version requirement, there is likely a reason for it, like MSRV. I shouldn't have to then run
cargo update -p clap --precise 4.1.3
after runningcargo add
.Proposed Solution
When the version requirement is precise, lock to it
Notes
I implemented support for this in cargo-edit's
cargo upgrade
, see killercup/cargo-edit#795The text was updated successfully, but these errors were encountered: