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.
eks-blueprints-rust-sdk
Failed to verify create's content against its repository
Verified 7 out of 8 files (includes 2 Cargo-generated).
- warning: Crate tarball has been published from a different commit than the commit tagged by git tag 'v0.1.2'.
- Create git tags after comitting any changes, and commit changes after bumping versions and running
cargo update
.
- Create git tags after comitting any changes, and commit changes after bumping versions and running
- error: Manifest properties don't match: package.build: crates.io=<unset>, orig=build.rs.
Files in the crates.io crate compared to the repository:
Cargo.lock
not found.
Looked for the crate in
sdks/rust/
. Fetchedhttps://github.com/zjaco13/multi-lang-eks-blueprints-cdk.git
ddd1cca65c0c76607907eb7e0bcf05462435b85d.Checked on 2024-07-24
This check is experimental.
- warning: Crate tarball has been published from a different commit than the commit tagged by git tag 'v0.1.2'.
Dependency async-stream 0.2 is significantly outdated
Upgrade to 0.3.6 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 prost 0.11 is outdated
Upgrade to 0.13.5 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency tonic 0.9 is outdated
Upgrade to 0.13.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency tonic-build 0.9 is outdated
Upgrade to 0.13.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
If some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance]
to their
status = "deprecated"Cargo.toml
.