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.

• prosa

  • Dependency opentelemetry 0.21 is significantly outdated

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

    opentelemetry versions

  • Dependency opentelemetry-otlp 0.14 is significantly outdated

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

    opentelemetry-otlp versions

  • Dependency tracing-opentelemetry 0.22 is significantly outdated

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

    tracing-opentelemetry versions

  • Dependency aquamarine 0.5 is outdated

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

    aquamarine versions

  • Dependency config 0.13 is outdated

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

    config versions

  • Dependency opentelemetry-stdout 0.2 is outdated

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

    opentelemetry-stdout versions

  • Dependency opentelemetry_sdk 0.21 is outdated

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

    opentelemetry_sdk versions

  • Imprecise dependency requirement async-http-proxy = 1

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

    async-http-proxy versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["network-programming", "config"] 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

  • Missing keywords

    Help users find your crates. Add keywords = ["service-oriented", "microservices", "processor", "adaptor", "architecture"] (up to 5) to the Cargo.toml. Best keywords are alternative terms or their spellings that aren't in the name or description. Also add a keyword that precisely categorizes this crate and groups it with other similar crates.

• prosa-utils

  • Could not fetch repository

    We've had trouble cloning git repo from https://github\.com/worldline/prosa\.git

    At the moment we only support git, and attempt fetching when we index a new release. Cloning is necessary for lib.rs to gather data that is missing on crates.io, e.g. to correctly resolve relative URLs in README files, which depend on repository layout and non-standard URL schemes of repository hosts.

  • Dependency opentelemetry 0.21 is significantly outdated

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

    opentelemetry versions

  • Dependency opentelemetry-otlp 0.14 is significantly outdated

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

    opentelemetry-otlp versions

  • Dependency tracing-opentelemetry 0.22 is significantly outdated

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

    tracing-opentelemetry versions

  • README missing from crate tarball

    Cargo sometimes fails to package the README file. Ensure the path to the README in Cargo.toml is valid, and points to a file inside the crate's directory.

  • Dependency opentelemetry-stdout 0.2 is outdated

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

    opentelemetry-stdout versions

  • Dependency opentelemetry_sdk 0.21 is outdated

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

    opentelemetry_sdk versions

  • Imprecise dependency requirement bytes = 1

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

    bytes versions

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["pro-sa", "github", "crates-io"] (up to 5) to the Cargo.toml. Best keywords are alternative terms or their spellings that aren't in the name or description. Also add a keyword that precisely categorizes this crate and groups it with other similar crates.

• cargo-prosa

  • Dependency aquamarine 0.5 is outdated

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

    aquamarine versions

  • Dependency config 0.13 is outdated

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

    config versions

  • Imprecise dependency requirement bytes = 1

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

    bytes versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["development-tools::cargo-plugins"] to the Cargo.toml.

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["service-bus", "cargo-command", "pro-sa", "framework", "package"] (up to 5) to the Cargo.toml. Best keywords are alternative terms or their spellings that aren't in the name or description. Also add a keyword that precisely categorizes this crate and groups it with other similar crates.

• prosa, cargo-prosa, prosa-utils

  • Dependency serde_yaml 0.9 has issues

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

    serde_yaml crate

• prosa, cargo-prosa, prosa-utils

  • Dependency thiserror 1 is slightly outdated

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

    thiserror versions

• prosa-macros

  • Could not fetch repository

    We've had trouble cloning git repo from https://github\.com/worldline/prosa\.git

  • Imprecise dependency requirement syn = 2

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

    syn versions

  • README missing from crate tarball

    Cargo sometimes fails to package the README file. Ensure the path to the README in Cargo.toml is valid, and points to a file inside the crate's directory.

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