killercup / killercup/cargo-edit
No workflow for upgrading recursive dependencies if root dependencies are up-to-date
Open
bug
cargo-upgrade
- Dominant language
- Rust
- Stars
- 3.5k
- Forks
- 166
- PR merge metrics
- No merged PRs in 30d
Description
The current design for `cargo upgrade` is as a replacement for `cargo update` but we only do recursive compatible upgrades if we modified one of the root crates. You can't just run `cargo upgrade` and upgrade the indirect dependencies.
Contributor guide
Research direction
The issue names no files, tests, or entry points. Start by tracing how `cargo upgrade` decides whether to update dependencies and compare that behavior with `cargo update`; done should include a defined workflow that upgrades indirect dependencies when root dependencies are already current.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100