Make `cargo outdated` part of cargo itself
In Rust ecosystem, one main concern for library developers is to not have semver breaking updates to their package, because of the fear that majority of the dependent packages not getting the routing updates that would follow a breaking update. There are two general solutions to this problem: 1. The old-school back-porting of updates, so that dependents on any API version would get all the routine updates. This solution can easily become a huge maintenance cost on library developers and is not a common practice in the Rust community at the moment. 2. Help owner of dependent packages to update their dependency versions and apply the changes needed, if any. This solution can be much less time consuming, and distributes the workload throughout the dependency chain. It also means that only the versions being used get the maintenance work needed, but not all theoretically-possible versions. So, in rustacean words: *you pay for what you use*. Based on this, I want to propose to add new features to help owners with keeping their dependencies up-to-date. Most of the functionality can be exposed via the `cargo update` command. ## Proposed Features * **Warn on dependencies stuck in older versions.** This would be a plain warning on `cargo update`. The feature would be enabled by default, but there will be an option to disable it; and there can be one release version of Cargo as transition period, where the option is disabled by-default, but there's a notice about the upcoming cha
Posted by behnam on Jul 20, 2017, 6:30 PM
Tags
Related issues
- Yeah PC was a horrible platform before Win2k, but there was a beautiful short time period when we had alternatives like Amiga, Atari, NeX...
- Living in a 200+ year old house, I've seen a lot of this first-hand through both planned and unplanned renovations and repairs.
- Is anything with the pebble time able to capture heart rate for historical data analysis?
- Datastar has evolved into a suite of tools [1].
- > real issue is that MSG is basically a public utility.
- Everything good is a slippery slope: every step in the right direction is bad if you overshoot.
Raise real-world problems, find people facing the same issue, and discuss solutions.4,500 issues0 comments
pricing (EdTech)
Yeah PC was a horrible platform before Win2k, but there was a beautiful short time period when we had alternatives like Amiga, Atari, NeX...
NewLiving in a 200+ year old house, I've seen a lot of this first-hand through both planned and unplanned renovations and repairs.
Is anything with the pebble time able to capture heart rate for historical data analysis?
Datastar has evolved into a suite of tools [1].
> real issue is that MSG is basically a public utility.
Everything good is a slippery slope: every step in the right direction is bad if you overshoot.
Status Update - May 2026
I think what you wrote makes sense, and you missed one critical aspect : shared access to excessively expensive capitalized facilities an...
Make `cargo outdated` part of cargo itself
In Rust ecosystem, one main concern for library developers is to not have semver breaking updates to their package, because of the fear that majority of the dependent packages not getting the routing updates that would follow a breaking update. There are two general solutions to this problem: 1. The old-school back-porting of updates, so that dependents on any API version would get all the routine updates. This solution can easily become a huge maintenance cost on library developers and is not a common practice in the Rust community at the moment. 2. Help owner of dependent packages to update their dependency versions and apply the changes needed, if any. This solution can be much less time consuming, and distributes the workload throughout the dependency chain. It also means that only the versions being used get the maintenance work needed, but not all theoretically-possible versions. So, in rustacean words: *you pay for what you use*. Based on this, I want to propose to add new features to help owners with keeping their dependencies up-to-date. Most of the functionality can be exposed via the `cargo update` command. ## Proposed Features * **Warn on dependencies stuck in older versions.** This would be a plain warning on `cargo update`. The feature would be enabled by default, but there will be an option to disable it; and there can be one release version of Cargo as transition period, where the option is disabled by-default, but there's a notice about the upcoming cha
Comments (0)
No comments yet. Start the discussion.