Repository navigation
chore: bump tokio to 1.54.1 for security fixes - #65
Merged
Merged
Conversation
This was referenced Oct 27, 2026
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
Bump Tokio from 1.53.1 to 1.54.1 in the workspace manifest and lockfile to include the AsyncFd I/O-safety fix (RUSTSEC-2026-0386) and require a version newer than the Interval race in 1.54.0 (RUSTSEC-2026-0384). Use stack pinning in the existing drain-wait test to satisfy the current CI Clippy lint.
Validated on the latest main with
cargo x check,cargo x test(including extended recovery tests), andcargo x lint(including dependency security checks).