fix(security): upgrade crossbeam-epoch to 0.9.20#305
Merged
Conversation
RUSTSEC-2026-0204 flags crossbeam-epoch 0.9.18. The OSV Security Scan in CI fails on this advisory, blocking unrelated PRs such as #303.
bug-ops
force-pushed
the
fix/crossbeam-epoch-rustsec-2026-0204
branch
from
July 25, 2026 15:23
134a5b5 to
b37fadd
Compare
bug-ops
enabled auto-merge (squash)
July 25, 2026 15:23
npm audit fix bumps brace-expansion, js-yaml, linkify-it, and shell-quote (via concurrently) to patched versions, resolving 5 high severity DoS advisories flagged by the OSV Security Scan.
nightly recently deprecated Atomic::fetch_update in favor of try_update, but try_update only stabilizes in 1.95.0, above this crate's 1.89.0 MSRV. RUSTFLAGS=-D warnings otherwise fails every build on a fresh nightly toolchain.
WASM Bundle Size Report
|
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
crossbeam-epoch0.9.18 -> 0.9.20 inCargo.lockto resolve RUSTSEC-2026-0204main, which in turn blocksCI Successon any PR built against the currentCargo.lock(e.g. ci: bump actions/setup-node from 6 to 7 #303), independent of what that PR actually changesTest plan
cargo build --workspace --all-featurescargo nextest run --workspace --all-features --lib --bins(944 passed)cargo auditno longer reports crossbeam-epoch