fix(deps): bump event-listener to 5.4.2 for RUSTSEC-2026-0221 - #679
Merged
Conversation
event-listener 5.4.1 allows `!Send` tags to cross thread boundaries via StackSlot (RUSTSEC-2026-0221). It is a transitive dependency, and the advisory is fixed upstream in 5.4.2. `cargo audit` and `osv-scanner` both fail on it, and both are required checks — so every open PR in this repo is blocked on this one lockfile entry regardless of its own content. Ten were blocked at the time of this commit. Lockfile-only, minimal: `cargo update -p event-listener --precise 5.4.2`. concurrent-queue drops out because 5.4.2 no longer depends on it. No other package version changed.
forkwright
pushed a commit
that referenced
this pull request
Aug 4, 2026
🤖 I have created a release *beep* *boop* --- ## [0.2.2](v0.2.1...v0.2.2) (2026-08-03) ### Bug Fixes * **deps:** bump event-listener to 5.4.2 for RUSTSEC-2026-0221 ([#679](#679)) ([ce56e10](ce56e10)) * **desktop:** stop the standalone lockfile drifting behind releases ([#675](#675)) ([f07ca78](f07ca78)) * **epignosis:** hold the book cross-reference test ids in one place ([#676](#676)) ([8f2b9d0](8f2b9d0)) * **lint:** mark the RFC 6598 range citation as a reviewed reference ([#669](#669)) ([9f56867](9f56867)) * **syndesis:** give each TLS identity test its own temp directory ([#674](#674)) ([a9ef578](a9ef578)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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
1 participant
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.
Finding
event-listener5.4.1 allows!Sendtags to cross thread boundaries viaStackSlot— RUSTSEC-2026-0221. It reaches this repo as a transitive dependency, and the advisory is fixed upstream in 5.4.2.Why this blocks everything
cargo auditandosv-scannerare both required checks here, and both fail on this single lockfile entry. That means every open PR in this repo is red regardless of its own content — the failure has nothing to do with the branch under test.osv-scanneritself reports the fix is available:Every other advisory in that scan is already triaged and filtered with a documented review-by date; this is the only unfiltered one.
Change
Lockfile-only, minimal and precise:
No other package version changed. In harmonia,
concurrent-queuealso drops out because 5.4.2 no longer depends on it; in theatron only the version and checksum lines move.Verification
CI is the verifier —
cargo auditandosv-scanneron this PR are the direct test of the fix, since they are the checks that currently fail.