Repository navigation
fix(ci): refresh dependencies for Clippy and advisories - #395
Merged
Merged
Conversation
This was referenced Oct 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Related to #394, whose CI exposed toolchain lint and dependency-advisory failures.
async-traitand affected compatible dependencies so the current stable Clippy no longer rejects generated async-trait methods withdouble_must_use.ctutils,rustls,rustls-webpki,tokio,webpki-roots, andzip.zipto 9.1 and handle its now-fallible entry-name decoding when importing IAM and bucket metadata archives.sigv4afeature: the published AWS SigV4 implementation still resolves vulnerablecrypto-bigint 0.5.5, and no patched compatible release is currently available. This removes SigV4a signing, including AWS S3 Multi-Region Access Point requests; the CLI does not currently document MRAP path support. Revisit once AWS publishes a patched SigV4a dependency stack.Verification
cargo fmt --all --check— passedcargo +stable clippy --workspace --all-targets --locked -- -D warnings— passedcargo test --workspace --locked— passedcargo deny check advisories— passedcargo +1.92.0 build --workspace --locked— passedgit diff --check— passedThis PR is separate from #394. After it lands, update/rebase #394 onto
mainto rerun its CI with the refreshed lockfile.