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.
aaa
Dependency clap 3.0.0-beta.5 is significantly outdated
Consider upgrading to 4.5.37 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 crossterm 0.22 is significantly outdated
Consider upgrading to 0.29.0 to get all the fixes and improvements.
In Cargo, different 0.x versions are considered incompatible, so this is a semver-major upgrade.
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"
).Users pay attention to the latest release date. Even if the crate is perfectly fine as-is, users may not know that.
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["text-processing"]
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.
Missing keywords
Help users find your crates. Add
keywords = ["aaa", "file", "color", "parameters", "body"]
(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.
rs3a
Imprecise dependency requirement regex = 1
Cargo does not always pick latest versions of dependencies! Specify the version as
regex = "1.11.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 keywords
Help users find your crates. Add
keywords = ["format", "rs3a", "header", "io", "rendering"]
(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.
bps
Dependency teloxide 0.9 is significantly outdated
Consider upgrading to 0.15.0 to get all the fixes and improvements.
Dependency pretty_env_logger 0.4 is outdated
Consider upgrading to 0.5.0 to get all the fixes and improvements.
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["web-programming"]
to theCargo.toml
.Missing keywords
Help users find your crates. Add
keywords = ["sticker", "bps", "config", "variables"]
(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.Using outdated edition for no reason
We estimate that this crate requires at least Rust 1.59, which is newer than the last 2018-edition compiler. You can upgrade without breaking any compatibility. Run
cargo fix --edition
and updateedition="…"
inCargo.toml
.Using the latest edition helps avoid old quirks of the compiler, and ensures Rust code has consistent syntax and behavior across all projects.
gitconf
Dependency inquire 0.2.1 is significantly outdated
Consider upgrading to 0.7.5 to get all the fixes and improvements.
Dependency simplelog 0.11.2 is significantly outdated
Consider upgrading to 0.12.2 to get all the fixes and improvements.
Dependency toml 0.5.8 is outdated
Consider upgrading to 0.8.22 to get all the fixes and improvements.
Dependency which 4.2.4 is outdated
Consider upgrading to 7.0.3 to get all the fixes and improvements.
If some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance]
to their
status = "deprecated"Cargo.toml
.