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.

• fluent-bundle

  • Dependency fluent-langneg 0.13 is slightly outdated

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

    In Cargo, different 0.x versions are considered incompatible, so this is a semver-major upgrade.

    fluent-langneg versions

  • Dependency rustc-hash 1 is a bit outdated

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

    rustc-hash versions

  • Dependency self_cell 0.10 is outdated

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

    self_cell versions

  • Imprecise dependency requirement rustc-hash = 1

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

    rustc-hash versions

• fluent-resmgr

  • Dependency rustc-hash 1 is a bit outdated

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

    rustc-hash versions

  • Dependency thiserror 1.0 is a bit outdated

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

    thiserror versions

  • Imprecise dependency requirement rustc-hash = 1

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

    rustc-hash versions

• fluent-syntax

  • Dependency thiserror 1.0 is a bit outdated

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

    thiserror versions

• fluent-fallback

  • Dependency rustc-hash 1 is a bit outdated

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

    rustc-hash versions

  • Imprecise dependency requirement rustc-hash = 1

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

    rustc-hash versions

• intl-memoizer

  • Dependency fluent-langneg 0.13 is slightly outdated

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

    fluent-langneg versions

• fluent-pseudo

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

    regex versions

• flow-control

  • 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

No issues found in: tzif fluent-testing fluent count-digits

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