Repository navigation
fix(deps): Bump yanked chacha20 and spin crates - #1208
Merged
Merged
Conversation
Moves chacha20 from the yanked 0.10.1 release to 0.10.2 and spin 0.9.8 to 0.9.9. chacha20 0.10.2 fixes the SSE2 backend of the ChaCha RNG using an SSE4.1 intrinsic, which rand's StdRng/ThreadRng exercises at runtime. Lockfile-only change. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AuStkboncZthMhFiUkCzDe
Contributor
There was a problem hiding this comment.
Copilot wasn't able to review any files in this pull request. Check if the Files changed in this pull request are included in default exclusions.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1208 +/- ##
=======================================
Coverage 83.57% 83.58%
=======================================
Files 112 112
Lines 14029 14029
=======================================
+ Hits 11725 11726 +1
+ Misses 2304 2303 -1 ☔ 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.
Requested by Ben in a daily maintenance routine.
Before:
Cargo.lockpinned two yanked crates:chacha20 0.10.1(yanked 2026-08-27), compiled in viarand 0.10(used byactix-httpand others), andspin 0.9.8, compiled in vialazy_static.cargo auditflags both as yanked.After:
chacha20is at 0.10.2 andspinis at 0.9.9, the next patch release in each series. chacha20 0.10.2 fixes the SSE2 backend of the ChaCha RNG using an SSE4.1 intrinsic (RustCrypto/stream-ciphers#580), which could fault with an illegal instruction on CPUs without SSE4.1.cargo auditno longer reports either crate as yanked.How:
cargo update -p chacha20 --precise 0.10.2andcargo update -p spin@0.9.8 --precise 0.9.9. This changes only the lockfile, with no manifest or code changes. Locally,cargo test --locked -p grey-apiand-p grey-uipass. For-p grey, I used a placeholderui/distbecause CI builds the UI with trunk first: 221 tests pass, and the only failures are the page and asset tests that need the real UI build and the DNS/TCP/TLS tests that need network access. CI covers both.🤖 Generated with Claude Code
https://claude.ai/code/session_01AuStkboncZthMhFiUkCzDe
Generated by Claude Code