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.
reef
Dependency rusqlite 0.30.0 is significantly outdated
Upgrade to 0.34.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
In Cargo, different 0.x versions are considered incompatible, so this is a semver-major upgrade.
Dependency strum 0.25 is significantly outdated
Upgrade to 0.27.1 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency strum_macros 0.25 is significantly outdated
Upgrade to 0.27.1 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency bincode 1.3.3 is slightly outdated
Consider upgrading to 2.0.0 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.Dependency colored 2.0 is a bit outdated
Consider upgrading to 3.0.0 to get all the fixes and improvements.
Dependency directories 5.0.1 is outdated
Consider upgrading to 6.0.0 to get all the fixes and improvements.
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["command-line-interface", "os"]
to theCargo.toml
.Even if there are no categories that fit precisely, pick one that is least bad. You can also propose new categories in crates.io issue tracker.
reel
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["…"]
to theCargo.toml
.Dependency directories 3.0 is significantly outdated
Upgrade to 6.0.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency error-chain 0.12 has issues
It may not be actively developed any more. Consider changing the dependency.
Dependency git2 0.13 is outdated
Upgrade to 0.20.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency reef 0.0.14 is slightly outdated
Consider upgrading to 0.1.17 to get all the fixes and improvements.
Latest stable release is old
It's been over 4 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
.