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.

• lets_expect

  • Imprecise dependency requirement tokio = 1

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

    tokio versions

  • Missing keywords

    Help users find your crates. Add keywords = ["testing", "expect", "test-framework", "assertions", "clean"] (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.

• lets_expect_core

  • Missing keywords

    Help users find your crates. Add keywords = ["…"] (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.

  • Dependency syn 1.0.103 is significantly outdated

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

    syn versions

  • Imprecise dependency requirement tokio = 1

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

    tokio versions

• lets_expect_assertions, lets_expect_core, lets_expect_macro

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

• lets_expect_assertions, lets_expect_core, lets_expect_macro

  • Could not fetch repository

    We've had trouble cloning git repo from https://github\.com/tomekpiotrowski/lets\_expect\.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.

• lets_expect_assertions

  • Missing keywords

    Help users find your crates. Add keywords = ["assertions", "testing", "lets-expect", "clean", "internal"] (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.

• lets_expect_macro

  • Dependency syn 1.0.103 is significantly outdated

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

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