Hi, I used
cargo upgrade about two months ago to upgrade the dependency versions in the
Cargo.toml of a project.
I recently upgraded to the latest
cargo edit and performed another project wide upgrade. But the 'upgrade' feature seems to have changed behavior dramatically.
I used to simply run 'cargo upgrade' in a workspace and it would update all dep semvers in the
Cargo.toml to the latest versions.
cargo upgrade is deciding to not upgrade the semver of a rep if it's compatible. Also some dependencies are classified as
locked but what that means isn't explained anywhere.
It seems that the expected workflow is to use
cargo update to update the lock file and then use
cargo upgrade --to-lockfile to change the semver's of the deps in the
I don't see a clear explanation on the repo readme or in the commits of why these changes were made and what the expected workflow is now.
It seems to be that changes are being made so that 'cargo upgrade' can eventually be merged into cargo and coexist/merge with 'cargo update'
Can anyone shed some light on the recent changes to
upgrade feature and what the expected workflow is now?