Repository navigation
build(deps): zstd 0.14.3, zstd-safe 8.2.0, zstd-sys 2.1.2, for RUSTSEC-2026-0391, -0398 and -0403 - #2627
Conversation
…C-2026-0391, -0398 and -0403 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NSAwDroXL6KqsSxUzdbZGw
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters: 1
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including
|
|
Approved: no findings at Nothing to do. Clobber: none. |
bryan-minimal
left a comment
There was a problem hiding this comment.
Lock-only, the three zstd crates and nothing else; cargo deny check advisories is clean with it on anvil too. Approving so the queue goes green again. The cherry-pick to release/0.7.0 after, as you say.
…-bigint, tokio) (#2630) * build(deps): zstd 0.14.3, zstd-safe 8.2.0, zstd-sys 2.1.2, for RUSTSEC-2026-0391, -0398 and -0403 (#2627) Claude-Session: https://claude.ai/code/session_01NSAwDroXL6KqsSxUzdbZGw Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> (cherry picked from commit 468a859) * build(deps): ctutils 0.4.5, for RUSTSEC-2026-0385 (#2503) * build(deps): ctutils 0.4.5, for RUSTSEC-2026-0385 A new advisory on ctutils 0.4.2 (non-constant-time mask generation and u128 comparisons; a transitive dependency through p256, ecdsa, elliptic-curve and crypto-bigint) fails cargo-deny on every pull request since this morning, so nothing can merge until the lock moves. Patched in 0.4.4; the lock takes 0.4.5. cargo deny check advisories is clean again and the workspace checks --locked. * chore(ci): re-run the cla status (cherry picked from commit c9114e1) * build(deps): crypto-bigint 0.7.7, for RUSTSEC-2026-0387 (#2517) (cherry picked from commit 20e25e4) * build(deps): tokio 1.53.3, for RUSTSEC-2026-0386 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NSAwDroXL6KqsSxUzdbZGw * fix(minimald): build AsyncFd with tokio's unsafe register tokio 1.53.3 deprecates AsyncFd::new as unsound (tokio-rs/tokio#8587), and clippy's -D warnings fails the build on it. Port main's fix from #2326 to both call sites, the PTY master and the tap device. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NSAwDroXL6KqsSxUzdbZGw * chore(release): bump version to 0.7.2 Hotfix release carrying the zstd, ctutils, crypto-bigint and tokio bumps (RUSTSEC-2026-0385, -0386, -0387, -0391, -0398, -0403) onto 0.7.1. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NSAwDroXL6KqsSxUzdbZGw --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: bryan-minimal <bryan@minimal.dev> Co-authored-by: Norrie Taylor <91171431+norrietaylor@users.noreply.github.com>
Summary
cargo-denyfails its advisories check on RUSTSEC-2026-0391, RUSTSEC-2026-0398 and RUSTSEC-2026-0403, so every merge-queue run is red. This PR runscargo update -p zstd -p zstd-safe -p zstd-sys. The change is toCargo.lockonly: zstd 0.14.0 → 0.14.3, zstd-safe 8.0.0 → 8.2.0, zstd-sys 2.1.0 → 2.1.2. No other package moves.Merge to main first. It then needs a cherry-pick to
release/0.7.0.Testing
just deny:advisories ok, bans ok, licenses ok, sources ok.cargo test -p common --locked: unit and integration tests pass.commonis the only crate that uses zstd directly. The doctests did not run in this sandbox becauserustdocis missing. CI covers them.🤖 Generated with Claude Code
https://claude.ai/code/session_01NSAwDroXL6KqsSxUzdbZGw