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.

• tetra

  • Dependency hashbrown 0.13.1 is significantly outdated

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

    hashbrown versions

  • Dependency glow 0.12.0 is outdated

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

    glow versions

  • Dependency image 0.24.1 is outdated

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

    image versions

  • Dependency rodio 0.17.1 is outdated

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

    rodio versions

  • Dependency sdl2 0.35.0 is outdated

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

    sdl2 versions

  • Dependency vek 0.15.4 is outdated

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

    vek versions

  • Optional dependency 'rodio' exposed as an implicit feature

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

    Crate features

• ogmo3

  • Dependency hashbrown 0.11 is significantly outdated

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

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

    If the crate is truly stable, why not make a 1.0.0 release?

    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.