Repository navigation
Update tokio to 1.54.1 for RUSTSEC-2026-0386 - #280
Merged
Merged
Conversation
RUSTSEC-2026-0386 marks tokio 1.52.3 unsound (AsyncFd constructors violate I/O safety), and cargo-deny now fails the dependency gate on main. 1.54.1 carries the fix. The workspace does not use AsyncFd.
Owner
Author
|
PR-Agent cannot review this PR: it drops |
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.
RUSTSEC-2026-0386 (published after #278's PR checks) marks tokio 1.52.3 unsound: the safe
AsyncFdconstructors violate I/O safety.cargo denynow fails the dependency gate on main, so the deploy gate refuses 4cbe177.Only the tokio entry in
Cargo.lockchanges (1.52.3 → 1.54.1, same dependency list). The workspace does not useAsyncFd.Checks:
cargo deny check(advisories, bans, licenses, sources ok),cargo clippy --workspace --all-targets --locked -- -D warnings.