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.
rust-i18n-support
Dependency globwalk 0.8.1 is significantly outdated
Upgrade to 0.9.1 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 itertools 0.11.0 is significantly outdated
Upgrade to 0.14.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Imprecise dependency requirement lazy_static = 1
Cargo does not always pick latest versions of dependencies! Specify the version as
lazy_static = "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.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 = ["internationalization"]
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 = ["yaml", "internationalization", "localization", "translation", "compile-time"]
(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.
rust-i18n-extract
Dependency serde_yml 0.0.11 is significantly outdated
Upgrade to 0.0.12 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency toml 0.7.4 is significantly outdated
Upgrade to 0.8.20 to get all the fixes, and avoid causing duplicate dependencies in projects.
Imprecise dependency requirement anyhow = 1
Cargo does not always pick latest versions of dependencies! Specify the version as
anyhow = "1.0.97"
. 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.This crate does not bump semver-minor when adding new features, so to be safe you get all the features/APIs/fixes that your crate depends on, require a more specific patch version.
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["internationalization"]
to theCargo.toml
.Missing keywords
Help users find your crates. Add
keywords = ["yaml", "internationalization", "localization", "translation", "extract"]
(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.
soundio-sys
Dependency bindgen 0.59 is significantly outdated
Upgrade to 0.71.1 to get all the fixes, and avoid causing duplicate dependencies in projects.
The Cargo package has no git commit information
Before publishing a package, make sure all packaged files are committed to the repository, and there are no "dirty" files. Push this commit to crate's public repository.
To protect against supply chain attacks similar to CVE-2024-3094, lib.rs will soon start flagging non-reproducible packages without public source code as suspicious. Currently only git repositories are supported (but may be hosted anywhere, not just GitHub). If you'd like a different SCM supported, please file a feature request.
*-sys crate without links property
If this crate uses C libraries with public symbols, consider adding
links = "soundio"
to crate'sCargo.toml
to avoid other libraries colliding with them. Note that the links property adds exclusivity to dependency resolution, but doesn't do any linking.This is also needed to protect your crate from duplicate older versions of itself. C symbols are global, and duplicate symbols can cause all sorts of breakage.
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?
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["multimedia::audio", "hardware-support"]
to theCargo.toml
.Missing keywords
Help users find your crates. Add
keywords = ["io-stream", "devices", "sample-rate", "bindings", "libsoundio"]
(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.
rust-i18n-macro
Imprecise dependency requirement serde = 1
Cargo does not always pick latest versions of dependencies! Specify the version as
serde = "1.0.218"
. 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 some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance]
to their
status = "deprecated"Cargo.toml
.