You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Update dependency versions in Cargo.toml to that of Cargo.lock #297
Sounds like a good idea -- especially for those projects where you don't want to keep running cargo -Z minimal-versions build and change the manifest manually :)
Maybe this can be a special mode in cargo-upgrade?
The --used flag in #41 (comment) seems relevant, I think, although cargo upgrade --to-lockfile would read a bit more fluently (but it's all a bikeshed).
Based on the feedback in prep for merging into cargo, we are looking at making cargo upgrade also do a cargo update which will remove some of the need for --to-lockfile.
We'll need to re-evaluate its place within cargo-upgrade and this issue might be re-opened as we might temporarily lose this functionality.
Activity
killercup commentedon May 29, 2019
Sounds like a good idea -- especially for those projects where you don't want to keep running
cargo -Z minimal-versions buildand change the manifest manually :)Maybe this can be a special mode in
cargo-upgrade?eddyb commentedon Jun 1, 2019
Without seeing this, I also thought this would be perfect for
cargo upgrade.The
--usedflag in #41 (comment) seems relevant, I think, althoughcargo upgrade --to-lockfilewould read a bit more fluently (but it's all a bikeshed).Merge #337
epage commentedon Sep 9, 2022
Based on the feedback in prep for merging into cargo, we are looking at making cargo upgrade also do a cargo update which will remove some of the need for
--to-lockfile.We'll need to re-evaluate its place within cargo-upgrade and this issue might be re-opened as we might temporarily lose this functionality.
fix(upgrade): Always upgrade compatible dependencies
epage commentedon Sep 9, 2022
See #786