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.

• duckdb

  • Dependency calamine 0.22.0 is significantly outdated

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

    calamine versions

  • Dependency strum 0.25 is significantly outdated

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

    strum versions

  • Dependency hashlink 0.9 is outdated

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

    hashlink versions

  • Imprecise dependency requirement arrow = 54

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

    arrow versions

  • Optional dependency 'duckdb-loadable-macros' exposed as an implicit feature

    Cargo automatically makes publicly-available crate features for every optional dependency, unless the dependencies are referenced using dep: syntax. Features 'duckdb-loadable-macros', 'r2d2', 'calamine', 'url', 'num', 'serde_json', 'chrono', 'uuid' may have been unintentional.

    Crate features

• libduckdb-sys

  • *-sys crate without links property

    If this crate uses C libraries with public symbols, consider adding links = "duckdb" to crate's Cargo.toml to avoid other libraries colliding with them. Note that the links property adds exclusivity to dependency resolution, but doesn't do any linking.

    This is also needed to protect your crate from duplicate older versions of itself. C symbols are global, and duplicate symbols can cause all sorts of breakage.

  • Optional dependency 'prettyplease' exposed as an implicit feature

    Cargo automatically makes publicly-available crate features for every optional dependency, unless the dependencies are referenced using dep: syntax. Features 'prettyplease', 'quote', 'cc', 'bindgen', 'syn' may have been unintentional.

    Crate features

No issues found in: duckdb-loadable-macros

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