Open reneleonhardt opened 1 month ago
FYI development focus has shifted to integrating this command into cargo.
Thx for letting me know. Do all feature cargo-edit requests now have to be addressed against cargo, or do we have to wait until the integration is finished, is there a milestone tracking progress?
https://github.com/rust-lang/cargo/issues/12425 is the issue for the current effort. Note that it isn't a drop-in replacement so requests like this won't make as much sense and might be better for https://github.com/rust-lang/cargo/issues/4309
Feature Request
Show technical debt numbers in
cargo upgrade
similar to like badges do to encourage increasing maintainability, minimizing vulnerabilities, improving code and using new features. The simplest number would be to sum up days between the installed version and the last stable release for all found upgrades (12 days between the old and new version of the first upgrade, 34 days between the old and new version of the second upgrade, ...). If you count compatible and incompatible updates separately you can show the reduced technical debt after a successful upgrade and the remaining technical debt for incompatible upgrades.Example:
Please note that crates.io already shows the age of a crate as the very first information below Metadata:
Other package managers like npm and bundler already offer an
outdated
command, this could be used internally bycargo upgrade
and offered as a public command as well.