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.

• retread

  • Dependency moka 0.11 is significantly outdated

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

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

    moka versions

  • Published crate doesn't match its repository

    Partially verified 36 files (includes 2 Cargo-generated).

    Fetched https://github.com/pileghoff/retread.git be60c4386d8dba83adec6ddf4f02187bce467d14.

    Checked on 2024-08-10

    This check is experimental.

    Forum thread

  • Dependency dap 0.3.1-alpha1 is outdated

    Consider upgrading to 0.4.1-alpha1 to get all the fixes and improvements.

    dap versions

  • Dependency thiserror 1.0 is a bit outdated

    Consider upgrading to 2.0.12 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

  • Imprecise dependency requirement log-panics = 2

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

    log-panics versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["development-tools::debugging"] 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 = ["choice", "retread", "debugging", "debug-adapter-protocol", "vscode-extension"] (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.

• ffi-mock-macro

  • Published crate doesn't match its repository

    Partially verified 4 files (includes 2 Cargo-generated).

    Looked for the crate in ffi-mock-macro/. Fetched https://github.com/pileghoff/ffi-mock.git 930dd05a344e7b0aa9055e041899b59458827046.

    Checked on 2024-08-04

    Forum thread

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

• free_async

  • Crate contains junk files

    The crate contains boilerplate Rust files with no real functionality.

No issues found in: ffi-mock

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