Issues found
Based on crates you own that have been published to crates.io. The best way to monitor these issues is to subscribe to the atom feed in your RSS reader.
sub-batch
Dependency which 5 is significantly outdated
Consider upgrading to 7.0.2 to get all the fixes and improvements.
Easy way to bump dependencies:
cargo install cargo-edit; cargo upgrade -i
; Also check out Dependabot service on GitHub.Imprecise dependency requirement anyhow = 1
Cargo does not always pick latest versions of dependencies! Specify the version as
anyhow = "1.0.97"
. IfCargo.lock
ends up having an unexpectedly old version of the dependency, you might get a dependency that lacks features/APIs or important bugfixes that you depend on. This is most likely to happen when using theminimal-versions
flag, used by users of old Rust versions.This crate does not bump semver-minor when adding new features, so to be safe you get all the features/APIs/fixes that your crate depends on, require a more specific patch version.
Dependency clap 2 is outdated
Consider upgrading to 4.5.31 to get all the fixes and improvements.
Dependency crossterm 0.27 is outdated
Consider upgrading to 0.28.1 to get all the fixes and improvements.
In Cargo, different 0.x versions are considered incompatible, so this is a semver-major upgrade.
Dependency interprocess 1 is outdated
Consider upgrading to 2.2.0 to get all the fixes and improvements.
Dependency rustyline 13 is outdated
Consider upgrading to 15.0.0 to get all the fixes and improvements.
the-daily-stallman
Dependency clap 2.33 is outdated
Consider upgrading to 4.5.31 to get all the fixes and improvements.
Dependency html5ever 0.25 is outdated
Consider upgrading to 0.29.1 to get all the fixes and improvements.
Dependency rss 1.9 is outdated
Consider upgrading to 2.0.12 to get all the fixes and improvements.
Dependency selectors 0.22 is outdated
Consider upgrading to 0.26.0 to get all the fixes and improvements.
Dependency ureq 2.0 is a bit outdated
Consider upgrading to 3.0.8 to get all the fixes and improvements.
Dependency which 4.0 is a bit outdated
Consider upgrading to 7.0.2 to get all the fixes and improvements.
Latest stable release is old
It's been over 3 years. Is this crate still maintained? Make a new release, either to refresh it, or to set
[badges.maintenance] status = "deprecated"
(or
"as-is"
,"passively-maintained"
).If the crate is truly stable, why not make a 1.0.0 release?
If some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance]
to their
status = "deprecated"Cargo.toml
.