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.

• fundamentum-edge-daemon

  • Dependency prost-wkt-types 0.5.1 is significantly outdated

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

    prost-wkt-types versions

  • Dependency tonic 0.11.0 is significantly outdated

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

    tonic versions

  • Dependency tonic-build 0.11.0 is significantly outdated

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

    tonic-build versions

  • Dependency clap-verbosity-flag 2.2.0 is outdated

    Consider upgrading to 3.0.2 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-verbosity-flag versions

  • Dependency derive-new 0.6.0 is outdated

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

    derive-new versions

  • Dependency fundamentum-sdk-mqtt 0.10.1 is outdated

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

    fundamentum-sdk-mqtt versions

  • Dependency itertools 0.13.0 is outdated

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

    itertools versions

  • Dependency prost 0.12.3 is outdated

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

    prost versions

  • Dependency tonic-reflection 0.11.0 is outdated

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

    tonic-reflection versions

• fundamentum-edge-proto

  • Dependency prost-wkt 0.5 is significantly outdated

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

    prost-wkt versions

  • Dependency prost-wkt-types 0.5 is significantly outdated

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

    prost-wkt-types versions

  • Dependency tonic 0.11 is significantly outdated

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

    tonic versions

  • Dependency tonic-build 0.11 is significantly outdated

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

    tonic-build versions

  • Dependency prost-wkt-build 0.5 is outdated

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

    prost-wkt-build versions

• fundamentum-edge-pfwd

  • Failed to verify create's content against its repository

    Could not check any files

    • warning: The crates.io package has no information about its path inside its repository.
    • error: Repository doesn't exist: Can't checkout the repository. It's either gone or private: remote authentication required but no callback set; class=Http (34); code=Auth (-16).
      • Make sure the repository URL in Cargo.toml is correct and works with git clone. The repository must be public.

    Checked on 2024-11-17

    This check is experimental.

    Forum thread

  • Dependency clap 3.2 is significantly outdated

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

    clap versions

  • Dependency derive-new 0.6 is outdated

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

    derive-new versions

  • Imprecise dependency requirement fundamentum-sdk-mqtt = 0

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

    fundamentum-sdk-mqtt versions

• fundamentum-sdk-mqtt

  • Dependency native-tls <0.2.14 is significantly outdated

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

    native-tls versions

  • Dependency derive_builder 0.12.0 is outdated

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

    derive_builder versions

  • Dependency jsonwebtoken 8.1 is outdated

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

    jsonwebtoken versions

  • Dependency prost 0.12.3 is outdated

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

    prost versions

  • Dependency thiserror 1 is a bit outdated

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

    thiserror versions

• fundamentum-edge-daemon, fundamentum-sdk-mqtt, fundamentum-edge-proto

  • Imprecise dependency requirement serde = 1

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

    This crate does not bump semver-minor when adding new features, so to be safe you get all the features/APIs/fixes that your crate depends on, require a more specific patch version.

    serde versions

• fundamentum-portforwarding-proto-rust

  • Failed to verify create's content against its repository

    Could not check any files

    • warning: The crates.io package has no information about its path inside its repository.
    • error: Repository doesn't exist: Can't checkout the repository. It's either gone or private: remote authentication required but no callback set; class=Http (34); code=Auth (-16).
      • Make sure the repository URL in Cargo.toml is correct and works with git clone. The repository must be public.

    Checked on 2024-07-24

    Forum thread

  • Locked dependency version enum-tags-traits =0.1.0

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    enum-tags-traits versions

  • Dependency derive-new 0.6.0 is outdated

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

    derive-new versions

  • Dependency prost-build 0.12 is outdated

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

    prost-build versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["network-programming"] to the Cargo.toml.

    Even if there are no categories that fit precisely, pick one that is least bad. You can also propose new categories in crates.io issue tracker.

    List of available categories

• fundamentum-edge-daemon, fundamentum-edge-pfwd, fundamentum-sdk-api, fundamentum-portforwarding-proto-rust

  • Dependency thiserror 1.0 is a bit outdated

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

    thiserror versions

• fundamentum-iot-mqtt-proto

  • Imprecise dependency requirement thiserror = 1

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

    thiserror versions

  • Dependency prost-build 0.12 is outdated

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

    prost-build versions

  • Dependency thiserror 1 is a bit outdated

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

    thiserror versions

• fundamentum-edge-proto, fundamentum-edge-pfwd, fundamentum-iot-mqtt-proto, fundamentum-portforwarding-proto-rust

  • Dependency prost 0.12 is outdated

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

    prost versions

• telit-me310g1

  • Dependency embassy-time 0.3 is outdated

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

    embassy-time versions

  • Dependency nom 7.1.3 is a bit outdated

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

    nom versions

• fundamentum-sdk-api

  • Dependency reqwest 0.11 is outdated

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

    reqwest versions

• fundamentum-edge-mcu-http-client

  • Dependency serde-json-core 0.5 is outdated

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

    serde-json-core versions

  • Dependency strum 0.26 is outdated

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

    strum versions

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