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.
prosemd-lsp
Dependency structopt 0.3 has issues
It has been losing active users, which may be a sign it's deprecated or obsolete. Consider replacing it with a different crate.
Dependency env_logger 0.8 is significantly outdated
Consider upgrading to 0.11.6 to get all the fixes and improvements.
In Cargo, different 0.x versions are considered incompatible, so this is a semver-major upgrade.
Dependency lru 0.6.5 is significantly outdated
Consider upgrading to 0.13.0 to get all the fixes and improvements.
Dependency tree-sitter 0.17.1 is significantly outdated
Consider upgrading to 0.25.3 to get all the fixes and improvements.
Dependency lspower 0.6.2 is outdated
Consider upgrading to 1.5.0 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 nlprule 0.4.6 is outdated
Consider upgrading to 0.6.4 to get all the fixes and improvements.
Dependency nlprule-build 0.4.6 is outdated
Consider upgrading to 0.6.4 to get all the fixes and improvements.
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?
README missing from crate tarball
Cargo sometimes fails to package the
README
file. Ensure the path to theREADME
inCargo.toml
is valid, and points to a file inside the crate's directory.
If some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance]
to their
status = "deprecated"Cargo.toml
.