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.
mq-workload-generator
Dependency rand 0.8 is a bit outdated
Consider upgrading to 0.9.0 to get all the fixes and improvements.
In Cargo, different 0.x versions are considered incompatible, so this is a semver-major upgrade.
Dependency rdkafka 0.36 is outdated
Consider upgrading to 0.37.0 to get all the fixes and improvements.
Dependency rustix 0.38 is outdated
Consider upgrading to 1.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 tokio = 1
Cargo does not always pick latest versions of dependencies! Specify the version as
tokio = "1.44.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 = ["development-tools::profiling"]
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.
rocketmq
Dependency opentelemetry 0.19.0 is significantly outdated
Upgrade to 0.28.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency tonic 0.9.0 is significantly outdated
Upgrade to 0.12.3 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency hostname 0.3.1 is outdated
Upgrade to 0.4.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency minitrace 0.4 is outdated
Upgrade to 0.6.7 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency mockall 0.11.4 is outdated
Upgrade to 0.13.1 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency opentelemetry-otlp 0.12.0 is outdated
Upgrade to 0.28.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency prost 0.11.8 is outdated
Upgrade to 0.13.5 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency prost-types 0.11.8 is outdated
Upgrade to 0.13.5 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency ring 0.16.20 is outdated
Upgrade to 0.17.14 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency siphasher 0.3.10 is outdated
Upgrade to 1.0.1 to get all the fixes, and avoid causing duplicate dependencies in projects.
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.24.0 is outdated
Upgrade to 0.26.2 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency tonic-build 0.9.0 is outdated
Upgrade to 0.12.3 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency which 4.4.0 is a bit outdated
Consider upgrading to 7.0.2 to get all the fixes and improvements.
Imprecise dependency requirement byteorder = 1
Cargo does not always pick latest versions of dependencies! Specify the version as
byteorder = "1.5.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.Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["network-programming"]
to theCargo.toml
.
If some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance]
to their
status = "deprecated"Cargo.toml
.