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.
prollytree
Dependency arrow 52.1.0 is significantly outdated
Upgrade to 55.1.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Easy way to bump dependencies:
cargo install cargo-edit; cargo upgrade -i
; Also check out Dependabot service on GitHub.Published crate doesn't match its repository
Partially verified 23 files (includes 3 Cargo-generated).
Files in the crates.io crate compared to the repository:
Cargo.lock
not found.
Fetched
https://github.com/zhangfengcdt/prollytree.git
0a82ef4e6f57b10d57e418b0f652a4324efd395d.Checked on 2024-08-04
This check is experimental.
Dependency bincode 1.3.3 is slightly outdated
Consider upgrading to 2.0.1 to get all the fixes and improvements.
Dependency rand 0.8.5 is a bit outdated
Consider upgrading to 0.9.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 thiserror 1.0.61 is a bit outdated
Consider upgrading to 2.0.12 to get all the fixes and improvements.
Dependency twox-hash 1.6 is slightly outdated
Consider upgrading to 2.1.0 to get all the fixes and improvements.
Latest prerelease is old
It's been over 9 months. 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"
).Users pay attention to the latest release date. Even if the crate is perfectly fine as-is, users may not know that.
If some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance]
to their
status = "deprecated"Cargo.toml
.