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.
howlong
Dependency bindgen 0.58 is significantly outdated
Upgrade to 0.71.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 errno 0.2 is significantly outdated
Upgrade to 0.3.10 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.
Easy way to bump dependencies:
cargo install cargo-edit; cargo upgrade -i; Also check out Dependabot service on GitHub.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?
pandoc-katex
Dependency toml 0.7 is significantly outdated
Consider upgrading to 0.8.20 to get all the fixes and improvements.
katex
Dependency derive_builder 0.12 is outdated
Upgrade to 0.20.2 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency itertools 0.10 is outdated
Upgrade to 0.14.0 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.
If some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance] to their
status = "deprecated"Cargo.toml.