Repository navigation
fix: update tokio for I/O safety advisory - #347
Merged
Merged
Conversation
Contributor
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
Updates Tokio from 1.53.2 to the patched 1.53.3, which clears RUSTSEC-2026-0386 (AsyncFd I/O unsoundness) and the failing cargo-deny advisories job seen on release PR #338. No advisory suppression or workflow changes.
Changes
tokioinCargo.lock.THIRD_PARTY_NOTICES.txtwithcargo run --bin notices.Review focus
Lockfile-only change; no parsing, matching or index builder code is touched, so no local gold run was done. CI gold quality and speed are still pending.
Checked locally:
cargo deny --all-features check advisories bans licenses sources,cargo fmt --check,cargo test --locked,cargo clippy --locked --all-targets -- -D warnings,git diff --check.