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.

• deku

  • Dependency rstest 0.22.0 is significantly outdated

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

    rstest versions

  • Dependency rustc-hash =2.1.0 is significantly outdated

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

    Easy way to bump dependencies: cargo install cargo-edit; cargo upgrade -i; Also check out Dependabot service on GitHub.

    rustc-hash versions

  • Optional dependency 'log' exposed as an implicit feature

    Cargo automatically makes publicly-available crate features for every optional dependency, unless the dependencies are referenced using dep: syntax. Feature 'log' may have been unintentional.

    Crate features

• variyak

  • Dependency seq-macro 0.2 is significantly outdated

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

    seq-macro versions

  • 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?

    Maintenance status field docs

• deku_derive

  • Dependency rstest 0.22 is significantly outdated

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

    rstest versions

  • Optional dependency 'proc-macro-crate' exposed as an implicit feature

    Cargo automatically makes publicly-available crate features for every optional dependency, unless the dependencies are referenced using dep: syntax. Feature 'proc-macro-crate' may have been unintentional.

    Crate features

• hachet

  • Crate is 'reserved'

    Please be respectful of crates.io and don't squat crate names.

    It's OK if you intend to publish this project in the near future. Keep in mind that even if you have good intentions, things may not go as planned. crates.io won't reclaim abandoned crates, so reserving good names may end up wasting the good names.

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