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.
dgraph-tonic
Dependency hyper-rustls 0.23 is significantly outdated
Upgrade to 0.27.5 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 tonic 0.8 is significantly outdated
Upgrade to 0.12.3 to get all the fixes, and avoid causing duplicate dependencies in projects.
Published crate doesn't match its repository
Verified 58 out of 59 files (includes 1 Cargo-generated).
- error: Manifest properties don't match: package.build: crates.io=<unset>, orig=build.rs.
- If you have a monorepo, you can use git tags in format
cratename/v0.11.0
- If you have a monorepo, you can use git tags in format
Fetched
https://github.com/selmeci/dgraph-tonic.git
taggedv0.11.0
(6c2e672383ab5fe1091ce1925386e59b7ba390bc).Checked on 2024-08-04
This check is experimental.
- error: Manifest properties don't match: package.build: crates.io=<unset>, orig=build.rs.
Dependency http 0.2 is outdated
Upgrade to 1.2.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.Dependency hyper 0.14 is outdated
Upgrade to 1.6.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency prost 0.11 is outdated
Upgrade to 0.13.5 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency rand 0.8 is a bit outdated
Consider upgrading to 0.9.0 to get all the fixes and improvements.
Dependency thiserror 1.0 is a bit outdated
Consider upgrading to 2.0.12 to get all the fixes and improvements.
Dependency tokio-rustls 0.23 is outdated
Upgrade to 0.26.2 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency tonic-build 0.8 is significantly outdated
Upgrade to 0.12.3 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency tower 0.4 is outdated
Upgrade to 0.5.2 to get all the fixes, and avoid causing duplicate dependencies in projects.
Imprecise dependency requirement tokio = 1
Cargo does not always pick latest versions of dependencies! Specify the version as
tokio = "1.43.0"
. 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.If you want to keep using truly minimal dependency requirements, please make sure you test them in CI with
-Z minimal-versions
Cargo option, because it's very easy to accidentally use a feature added in a later version.Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["database"]
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.
cascara
Dependency indexmap 1.9 is outdated
Upgrade to 2.7.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency rand 0.8 is a bit outdated
Consider upgrading to 0.9.0 to get all the fixes and improvements.
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["caching"]
to theCargo.toml
.
dgraph-rs-http
No repository property
Specify git repository URL in
Cargo.toml
to help users find more information, contribute, and for lib.rs to read more info.Dependency rand 0.6 is significantly outdated
Upgrade to 0.9.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency reqwest 0.9.11 is significantly outdated
Upgrade to 0.12.12 to get all the fixes, and avoid causing duplicate dependencies in projects.
Latest stable release is old
It's been over 5 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?
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["web-programming::http-client"]
to theCargo.toml
.Missing keywords
Help users find your crates. Add
keywords = ["http-client", "dgraph", "note"]
(up to 5) to theCargo.toml
. Best keywords are alternative terms or their spellings that aren't in the name or description. Also add a keyword that precisely categorizes this crate and groups it with other similar crates.
If some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance]
to their
status = "deprecated"Cargo.toml
.