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.

• dti

  • Imprecise dependency requirement serde = 1

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

  • Dependency reqwest 0.11 is outdated

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

    reqwest versions

  • Dependency thiserror 1 is a bit outdated

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

  • Failed to verify create's content against its repository

    Verified 10 out of 11 files (includes 2 Cargo-generated).

    • warning: The crates.io package has no information about its path inside its repository.
    • warning: There is no matching git tag containing version '0.1.2'.
    • error: Manifest properties don't match: Number of [[bin]] inconsistent; published=0; orig=1; ed=Set(E2021).

    Files in the crates.io crate compared to the repository:

    • Cargo.lock not found.

    Fetched https://gitlab.com/21analytics/dti.git 7de31c80e294342acc1e089fd39cf0affe708d39.

    Checked on 2024-07-24

    This check is experimental.

    Forum thread

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