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.

• venv-wrapper

  • Dependency ansi_term ~0.12.1 has issues

    It may not be actively developed any more. Consider changing the dependency.

    ansi_term crate

  • Dependency clap ~2.33 is significantly outdated

    Consider upgrading to 4.5.27 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.

    clap versions

  • Dependency directories ~3.0.2 is significantly outdated

    Consider upgrading to 6.0.0 to get all the fixes and improvements.

    directories versions

  • Dependency env_logger ~0.8.4 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.

    env_logger versions

  • Dependency rust-ini ~0.17 is significantly outdated

    Consider upgrading to 0.21.1 to get all the fixes and improvements.

    rust-ini versions

  • Dependency which ~4.2.2 is significantly outdated

    Consider upgrading to 7.0.1 to get all the fixes and improvements.

    which versions

  • Imprecise dependency requirement regex = ~1

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

    If you want to keep using truly minimal dependency requirements, please make sure you test them in CI with -Z minimal-versions Cargo option, because it's very easy to accidentally use a feature added in a later version.

    regex versions

  • 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").

    Users pay attention to the latest release date. Even if the crate is perfectly fine as-is, users may not know that.

    Maintenance status field docs

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