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.

• sentinel-core

  • Dependency k8s-openapi 0.16.0 is significantly outdated

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

    k8s-openapi versions

  • Dependency kube 0.76 is significantly outdated

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

    kube versions

  • Dependency lru 0.7.5 is significantly outdated

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

    lru versions

  • Dependency serde_yaml 0.8.23 has issues

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

    serde_yaml crate

  • Dependency sysinfo 0.26.8 is significantly outdated

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

    sysinfo versions

  • Dependency base64 0.13 is outdated

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

    base64 versions

  • Dependency directories 4.0.1 is outdated

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

    directories versions

  • Dependency env_logger 0.9.0 is outdated

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

    env_logger versions

  • Dependency etcd-rs 0.6 is slightly outdated

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

    etcd-rs versions

  • Imprecise dependency requirement log4rs = 1

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

    log4rs versions

  • Optional dependency 'k8s-openapi' 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 'k8s-openapi', 'kube', 'prometheus_exporter', 'base64', 'directories', 'futures', 'regex', 'consul', 'env_logger', 'schemars', 'etcd-rs', 'log4rs', 'sentinel-macros' may have been unintentional.

    Crate features

• sentinel-motore

  • Latest stable release is old

    It's been over 2 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").

    Nightly crates tend to have a short lifespan. We're delisting them if they're not updated frequently.

    Maintenance status field docs

  • Dependency motore 0.2.1 is outdated

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

    motore versions

  • Dependency volo 0.2 is outdated

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

    volo versions

• sentinel-actix

  • Imprecise dependency requirement actix-web = 4

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

    actix-web versions

• sentinel-tonic

  • Dependency tonic 0.8.2 is significantly outdated

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

    tonic versions

• sentinel-tower

  • Dependency http 0.2 is outdated

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

    http versions

  • Dependency tower 0.4 is outdated

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

    tower versions

• sentinel-macros

  • Dependency darling 0.13.1 is significantly outdated

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

    darling versions

  • Dependency syn 1.0.74 is significantly outdated

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

    syn 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

No issues found in: sentinel-rocket

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