Lib.rs

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.

• feature-factory, vq

  • Imprecise dependency requirement thiserror = 2

    Cargo does not always pick latest versions of dependencies! Specify the version as thiserror = "2.0.12". If Cargo.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 the minimal-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.

    thiserror versions

• graphina

  • Dependency ctor 0.3.6 is significantly outdated

    Upgrade to 0.4.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.

    ctor versions

• template-rust-project

  • Dependency ctor 0.2.9 is outdated

    Upgrade to 0.4.1 to get all the fixes, and avoid causing duplicate dependencies in projects.

    ctor versions

No issues found in: spart

If some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance]
status = "deprecated" to their Cargo.toml.