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.
transient
Dependency ndarray 0.15 is outdated
Consider upgrading to 0.16.1 to get all the fixes and improvements.
In Cargo, different 0.x versions are considered incompatible, so this is a semver-major upgrade.
Dependency numpy 0.21 is outdated
Upgrade to 0.23.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Imprecise dependency requirement either = >=1
Cargo does not always pick latest versions of dependencies! Specify the version as
either = "1.13.0"
. IfCargo.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 theminimal-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.Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["rust-patterns"]
to theCargo.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.
Optional dependency 'transient-derive' exposed as an implicit feature
Cargo automatically makes publicly-available crate features for every optional dependency, unless the dependencies are referenced using
dep:
syntax. Feature 'transient-derive' may have been unintentional.
transient-derive
Could not fetch repository
We've had trouble cloning git repo from
https://github\.com/jrrudy1/transient\.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.
Imprecise dependency requirement syn = 2
Cargo does not always pick latest versions of dependencies! Specify the version as
syn = "2.0.90"
. IfCargo.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 theminimal-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.
No readme property
Specify path to a
README
file for the project, so that information about is included in the crates.io tarball.Published crate doesn't match its repository
Verified 40 out of 42 files (includes 2 Cargo-generated).
Files in the crates.io crate compared to the repository:
LICENSE-APACHE
does not match the repository.LICENSE-MIT
does not match the repository.derive/
LICENSE-MIT
exists, but elsewhere in the repo.LICENSE-APACHE
exists, but elsewhere in the repo.
Looked for the crate in
derive/
. Fetchedhttps://github.com/jrrudy1/transient.git
taggedv0.4.1
(acdbdee6780233aaeb114a485e0856baa2f87b38).Checked on 2024-09-09
This check is experimental.
Dependency thiserror 1 is slightly outdated
Consider upgrading to 2.0.7 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.
If some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance]
to their
status = "deprecated"Cargo.toml
.