chore(deps): update chacha20 to 0.10.2 and drop the yank exception - #165
Merged
Merged
Conversation
chacha20 0.10.0 and 0.10.1 are both yanked upstream (a yank, not an advisory). 0.10.2 was published 2026-08-27 and has now cleared the 7-day hold on fresh releases, so take it and remove the stop-gap ignore that #161 added to deny.toml. The crate is transitive only, via rand 0.10.2 under sqlx-postgres and axum-test. The e2e workspace keeps its own lockfile and pinned the same yanked version, so bump it too — cargo-deny only scans the root, but there is no reason to leave the second lock on a yanked release. Closes #162 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #165 +/- ##
=======================================
Coverage 96.31% 96.31%
=======================================
Files 28 28
Lines 13132 13132
=======================================
Hits 12648 12648
Misses 484 484 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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.
chacha200.10.0 and 0.10.1 are both yanked upstream — a yank, not a securityadvisory (the only RUSTSEC entry for the crate, RUSTSEC-2019-0029, is against
0.1.x). 0.10.2 was published 2026-08-27 and has now cleared the 7-day hold on
fresh releases, so this takes it and removes the stop-gap
advisories.ignoreentry that #161 added to
deny.toml.The crate is transitive only, via
rand 0.10.2undersqlx-postgresandaxum-test:The
e2e/workspace keeps its own lockfile and pinned the same yanked version,so it is bumped too. CI only runs
cargo deny checkat the repository root, sothat lock was not failing anything — there is just no reason to leave a second
lockfile on a yanked release.
Lockfiles and config only; no source change, hence no test — nothing about the
program's behaviour changes. README screenshots are unaffected (no template,
CSS or rendered copy in the diff).
Verification
cargo deny check(exit 0):cargo nextest run(exit 0):cd e2e && cargo check --all-targets(exit 0):Closes #162
🤖 Generated with Claude Code