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.

• fnck_sql

  • Dependency itertools 0.12 is significantly outdated

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

    itertools versions

  • Dependency sqlparser 0.34 is significantly outdated

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

    sqlparser versions

  • Dependency dirs 5 is outdated

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

    dirs versions

  • Dependency fixedbitset 0.4 is outdated

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

    fixedbitset versions

  • Dependency ordered-float 4 is outdated

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

    ordered-float versions

  • Dependency petgraph 0.6 is a bit outdated

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

    petgraph versions

  • Dependency pgwire 0.19 is outdated

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

    pgwire versions

  • Dependency rocksdb 0.22 is outdated

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

    rocksdb versions

  • Imprecise dependency requirement bumpalo = 3

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

    bumpalo versions

• kite_sql

  • Dependency itertools 0.12 is significantly outdated

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

    itertools versions

  • Dependency sqlparser 0.34 is significantly outdated

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

    sqlparser versions

  • docs.rs build failed

    docs.rs site failed to build the crate, so users will have trouble finding the documentation. Docs.rs supports multiple platforms and custom configurations, so you can make the build work even if normal crate usage has special requirements.

    Docs.rs doesn't need to run or even link any code, so system dependencies can simply be skipped. You can also set cfg() flags just for docs.rs and use them to hide problematic code.

    Detecting docs.rs

  • Dependency dirs 5 is outdated

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

    dirs versions

  • Dependency fixedbitset 0.4 is outdated

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

    fixedbitset versions

  • Dependency ordered-float 4 is outdated

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

    ordered-float versions

  • Dependency petgraph 0.6 is a bit outdated

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

    petgraph versions

  • Dependency rocksdb 0.22 is outdated

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

    rocksdb versions

  • Imprecise dependency requirement bumpalo = 3

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

    bumpalo versions

• kip_db

  • Dependency tonic 0.10.2 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.10.2 is significantly outdated

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

    tonic-build versions

  • Dependency integer-encoding 3.0.4 is a bit outdated

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

    integer-encoding versions

  • Dependency itertools 0.10.3 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 is outdated

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

    prost versions

  • Dependency rand 0.8.5 is a bit outdated

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

    rand versions

  • Dependency rocksdb 0.21.0 is outdated

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

    rocksdb versions

  • Dependency thiserror 1.0.24 is a bit outdated

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

    thiserror versions

  • Latest prerelease is old

    It's been over 10 months. Is this crate still maintained? Make a new release, either to refresh it, or to set

    [badges.maintenance]
    status = "deprecated"
    

    (or "as-is", "passively-maintained").

    Nightly crates tend to have a short lifespan. We're delisting them if they're not updated frequently.

    Maintenance status field docs

• issue-hunter

  • Dependency prettytable-rs 0.1 is significantly outdated

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

    prettytable-rs versions

  • Imprecise dependency requirement anyhow = 1

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

    anyhow versions

  • Dependency dirs 5 is outdated

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

    dirs versions

  • Dependency reqwest 0.11 is outdated

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

    reqwest versions

• kip-sql

  • Dependency sqlparser 0.34.0 is significantly outdated

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

    sqlparser versions

  • Latest prerelease is old

    It's been over 13 months. Is this crate still maintained? Make a new release, either to refresh it, or to set

    [badges.maintenance]
    status = "deprecated"
    

    (or "as-is", "passively-maintained").

    Maintenance status field docs

  • Dependency integer-encoding 3.0.4 is a bit outdated

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

    integer-encoding versions

  • Dependency itertools 0.10 is outdated

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

    itertools versions

  • Dependency mlua 0.9.1 is outdated

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

    mlua versions

  • Dependency ordered-float 3.0 is outdated

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

    ordered-float versions

  • Dependency petgraph 0.6.3 is a bit outdated

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

    petgraph versions

  • Dependency strum_macros 0.24 is outdated

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

    strum_macros versions

  • Failed to verify create's content against its repository

    Verified 162 out of 167 files (includes 4 Cargo-generated).

    • warning: The crates.io package has no information about its path inside its repository.
    • warning: Crate tarball has been published from the commit fe49bc860108c2891bcba8e3e30d1a9053da0d9f, which is not in the repository.
      • Create git tags after comitting any changes, and commit changes after bumping versions and running cargo update.
    • warning: There is no matching git tag containing version '0.0.1-alpha.8'.
    • warning: Had to perform fuzzy search of the head branch due to lack of commit information in the package.

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

    • Cargo.lock not found.
    • Cargo.toml.orig does not match the repository.
    • .gitignore does not match the repository.
    • query_benchmark.rs does not match the repository.
    • db.rs does not match the repository.
    • mod.rs does not match the repository.
    • mod.rs does not match the repository.

    Fetched https://github.com/kipdata/kipsql.git 890c5bbb2b24f612d4e36e33d09eeebf1e51ebc7.

    Checked on 2024-08-16

    This check is experimental.

    Forum thread

  • Imprecise dependency requirement csv = 1

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

    csv versions

• fnck_sql, kite_sql, kip-sql

  • Dependency thiserror 1 is a bit outdated

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

    thiserror versions

• kite_sql_serde_macros, fnck_sql_serde_macros, tonbo_marco

  • No repository property

    Specify git repository URL in Cargo.toml to help users find more information, contribute, and for lib.rs to read more info.

• kite_sql_serde_macros

  • No readme property

    Specify path to a README file for the project, so that information about is included in the crates.io tarball.

• kite_sql_serde_macros, fnck_sql_serde_macros, tonbo_marco

  • Imprecise dependency requirement syn = 2

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

    syn versions

• fnck_sql_serde_macros

  • No readme property

    Specify path to a README file for the project, so that information about is included in the crates.io tarball.

• tonbo_marco

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