chore(deps): Bump tokio from 1.52.3 to 1.53.1

[dependabot]

Bumps tokio from 1.52.3 to 1.53.1.

Release notes

Sourced from tokio's releases.

Tokio v1.53.1

1.53.1 (July 20th, 2026)

Fixed

• signal: restore MSRV by removing OnceLock::wait from the Windows handler (#8300)

Fixed (unstable)

• time: fix alt timer cancellation and insertion race (#8252)

Documented

• runtime: remove dead link definition in Runtime::block_on (#8301)

#8252: tokio-rs/tokio#8252 #8300: tokio-rs/tokio#8300 #8301: tokio-rs/tokio#8301

Tokio v1.53.0

1.53.0 (July 17th, 2026)

Added

• fs: implement From<OwnedFd> and From<OwnedHandle> for File (#8266)
• metrics: add task schedule latency metric (#7986)
• net: add SocketAddr methods to Unix sockets (#8144)

Changed

• io: add #[inline] to IO trait impls for in-memory types (#8242)
• net: implement UCred::pid on FreeBSD (#8086)
• net: support Nuttx target os (#8259)
• signal: refactor global variables on Windows (#8231)
• sync: mpsc::{Receiver,UnboundedReceiver} now drops waker on drop, even if there are still senders (#8095)
• taskdump: support taskdumps on s390x (#8192)
• time: add #[track_caller] to timeout_at() (#8077)
• time: consolidate mutex locks on spurious poll (#8124)
• time: defer waker clone on spurious poll (#8107)
• time: move lazy-registration state into Sleep (#8132)
• tracing: remove unnecessary span clone (#8126)

Fixed

• io: do not treat zero-length reads as EOF in Chain (#8251)
• net: use getpeereid for QNX peer credentials (#8270)
• runtime: avoid illegal state in FastRand (#8078)
• sync: wake mpsc receiver when a queued reserve[_many] returns permits (#8260)
• taskdump: skip double wake on Trace::capture/Trace::trace_with (#8043)
• time: avoid stack overflow in runtime constructor (#8093)

... (truncated)

Commits

• 75fef53 chore: prepare Tokio v1.53.1 (#8303)
• ae9d011 signal: restore MSRV by removing OnceLock::wait from the Windows handler (#8300)
• eb4988d time: fix the loom test of the race between cancellation/insertion (#8302)
• 91d3b4c time: fix alt timer cancellation and insertion race (#8252)
• a463384 runtime: remove dead link definition in Runtime::block_on (#8301)
• be689a3 chore: prepare Tokio v1.53.0 (#8294)
• 50f76c7 chore: prepare tokio-macros v2.7.1 (#8295)
• f61fcca Merge 'tokio-1.52.4' into 'master' (#8290)
• efdba5f chore: prepare Tokio v1.52.4 (#8289)
• b0ba02e Merge 'tokio-1.51.4' into 'tokio-1.52.x' (#8288)
• Additional commits viewable in compare view

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	cargo/​tokio@​1.53.1

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: cargo tokio is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: Cargo.lock → cargo/tokio@1.53.1 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore cargo/tokio@1.53.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[msalvatti]

@dependabot rebase

[msalvatti]

Status: blocked on the supply-chain policy, not on anything wrong with this bump.

cargo deny and cargo audit pass here — no known advisory, no license or ban issue. The only failing step is cargo vet, and it is failing because the new version has no audit yet from any source this repository imports.

#117 has landed and separates the two causes that were tangled together. It refreshed supply-chain/imports.lock, which was five dependencies behind and was making every PR fail for reasons that had nothing to do with the PR, and it pinned CI to cargo vet --locked so the gate answers from what the repository recorded rather than from whatever upstream published that minute. What is left here is genuinely this bump:

$ cargo vet          # with the imports refreshed
Vetting Failed!

(the exact crate is listed in the job log)

Three ways forward, and the right one is a call for the maintainer rather than something to route around:

1. Wait. This is what just happened for anyhow, serde_json, syn and thiserror: Mozilla, Bytecode Alliance and Google published audits between 18 and 22 July, and the versions became vetted with no decision from us. There is no advisory here, so waiting costs nothing.
2. Audit the diff with cargo vet diff, and record it with cargo vet certify. Honest, and real work — the redis 1.3 → 1.5 diff alone is 2377 insertions.
3. Exempt it — record that we accept the version without auditing it. Fastest, and the only one that puts a trust claim in the repository that nobody earned.

Leaving this open rather than forcing it through: a gate that gets bypassed whenever it is inconvenient is not a gate.