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.
voltdb-client-rust
Dependency sha2 0.9.8 is significantly outdated
Upgrade to 0.10.8 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 bigdecimal 0.3.0 is outdated
Upgrade to 0.4.7 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency bytebuffer-rs 0.3.1 is outdated
Upgrade to 2.0.1 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.Incorrect category
Crate's categories property in
Cargo.toml
contains 'voltdb', which isn't a category we recognizelib.rs has simplified and merged some of crates.io categories. Please file a bug if we got it wrong.
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?
Published crate contains binary files
The crate contains binary files (JAR file). Crates are meant to be compiled from source. Please check that you haven't published temporary build files by accident. If you have test fixtures, consider excluding them from crates-io tarball, since Cargo doesn't run tests from crates-io packages.
If some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance]
to their
status = "deprecated"Cargo.toml
.