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.
test-context-macros
Published crate doesn't match its repository
Verified 4 out of 5 files (includes 1 Cargo-generated).
- error: Manifest properties don't match: package.version.
- If you have a monorepo, you can use git tags in format
cratename/v0.4.1
- If you have a monorepo, you can use git tags in format
Looked for the crate in
test-context-macros/
. Fetchedhttps://github.com/jasterv/test-context.git
64a4e1ba7f5bbba0582ea25bef771be972ebf361.Checked on 2025-02-02
This check is experimental.
- error: Manifest properties don't match: package.version.
Imprecise dependency requirement syn = ^2
Cargo does not always pick latest versions of dependencies! Specify the version as
syn = "2.0.101"
. 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.
rocket_sentry_logger
Latest stable release is old
It's been over 4 years. 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.
Dependency sentry 0.22.0 is significantly outdated
Upgrade to 0.38.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.
Dependency rocket 0.4.7 is outdated
Upgrade to 0.5.1 to get all the fixes, and avoid causing duplicate dependencies in projects.
No issues found in: test-context
If some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance]
to their
status = "deprecated"Cargo.toml
.