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.
jqdata
Dependency mockito 0.23 is significantly outdated
Upgrade to 1.6.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency reqwest 0.10 is significantly outdated
Upgrade to 0.12.12 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.
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["authentication"]
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.
jqdata-model, jqdata-blocking, aosa
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["…"]
to theCargo.toml
.
jqdata-blocking
Dependency mockito 0.23 is significantly outdated
Upgrade to 1.6.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency reqwest 0.10 is significantly outdated
Upgrade to 0.12.12 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency jqdata-derive 0.1.0 is outdated
Upgrade to 0.2.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
jqdata-model
Dependency bigdecimal =0.1.0 is significantly outdated
Upgrade to 0.4.7 to get all the fixes, and avoid causing duplicate dependencies in projects.
Locked dependency version bigdecimal =0.1.0
This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.
semistr
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["algorithms"]
to theCargo.toml
.
jqdata, jqdata-model, jqdata-blocking, jqdata-derive
Latest stable release is old
It's been over 4 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?
jqdata-derive
Dependency syn 1.0 is significantly outdated
Upgrade to 2.0.98 to get all the fixes, and avoid causing duplicate dependencies in projects.
If some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance]
to their
status = "deprecated"Cargo.toml
.