chore(deps): bump futures-util from 0.3.33 to 0.3.34

[dependabot]

Bumps futures-util from 0.3.33 to 0.3.34.

Release notes

Sourced from futures-util's releases.

0.3.34

• Preserve cloned waker identity. (#3032)
• Updato syn to 3. (#3028)

Changelog

Sourced from futures-util's changelog.

0.3.34 - 2026-08-11

• Preserve cloned waker identity. (#3032)
• Updato syn to 3. (#3028)

Commits

• 705e6b5 Release 0.3.34
• 616dac7 compat: Inline RawWaker clone function
• 4176369 Inline remaining RawWaker clone functions
• f17a895 Fix cloned FuturesUnordered waker identity
• 51d62ad macro: bump syn to v3 (#3028)
• 9e26177 ci: Reduce timeout-minutes
• b2d0983 tsan: Enable Adaptive Delay
• f733d0e Miri: Ignore compat tests
• e5def2f Rename default branch to main
• See full diff in compare view

[github-actions]

Thanks @dependabot[bot] for taking the time to contribute.

This repository is observing a maintainer-managed PR intake gate in dry-run mode, so this pull request is staying open. This note helps maintainers prepare the allowlist before any enforcement is considered.

Please read CONTRIBUTING.md for the expected contribution shape. A maintainer can grant recurring PR access by commenting /lgtm on a pull request.

[claude]

Claude finished @Hmbown's task in 31s —— View job

---

Review: chore(deps): bump futures-util 0.3.33 → 0.3.34

• Gather context and read the diff
• Check changed files (Cargo.lock only)
• Verify dependency graph impact (syn version)
• Post review

Summary: This is a lockfile-only dependency bump (Cargo.lock, +15/-15) with no source code changes. futures-channel, futures-core, futures-io, futures-macro, futures-sink, futures-task, and futures-util all move from 0.3.33 → 0.3.34 in lockstep, consistent with the upstream release notes (waker-identity fix in FuturesUnordered, syn bumped to v3 for the macro crate).

Findings, in priority order:

1. Correctness bugs: None — no source files changed, nothing to break compilation or introduce logic errors.
2. Provider/model/route safety (EPIC v0.8.65 EPIC: Separate provider facts, model facts, offerings, and route resolution #2608): Not applicable — this diff touches no provider/model/routing code.
3. Reuse/simplification: futures-macro now depends on syn 3.0.3 instead of syn 2.0.119. I checked and syn 3.0.3 was already present in the lockfile before this PR (used by ~14 other crates), so this doesn't introduce a new duplicate major version — if anything it converges one more consumer onto the already-present syn 3 line rather than the older syn 2.0.119/syn 1.0.109 still used elsewhere. No action needed.
4. Tests: N/A for a lockfile-only bump.
5. Security: Checksums in the diff match the versions bumped; this is a routine patch release from rust-lang/futures-rs with no advisory associated.

No blocking issues. Safe to merge from a code-correctness standpoint.

[claude]

Claude finished @Hmbown's task in 31s —— View job

---

Review: chore(deps): bump futures-util 0.3.33 → 0.3.34

• Gather context and re-check diff (branch was synchronized)
• Verify Cargo.lock changes
• Post review

Summary: The branch was synchronized via a merge from main (commit 72afb6a), but this introduced no new source changes — the diff against origin/main is still the identical lockfile-only bump (Cargo.lock, +15/-15) originally reviewed. No code files are touched.

futures-channel, futures-core, futures-io, futures-macro, futures-sink, futures-task, and futures-util all move from 0.3.33 → 0.3.34 in lockstep, matching upstream's release (waker-identity fix in FuturesUnordered, syn bumped to v3 for the macro crate).

Findings, in priority order:

1. Correctness bugs: None — no source files changed.
2. Provider/model/route safety (EPIC v0.8.65 EPIC: Separate provider facts, model facts, offerings, and route resolution #2608): Not applicable — no provider/model/routing code touched.
3. Reuse/simplification: futures-macro now depends on syn 3.0.3 instead of syn 2.0.119. Re-verified post-merge: syn 3.0.3 (along with 1.0.109 and 2.0.119) was already present in Cargo.lock before this bump, so no new duplicate major version is introduced.
4. Tests: N/A for a lockfile-only bump.
5. Security: Checksums in the diff match the bumped versions; routine patch release from rust-lang/futures-rs with no associated advisory.

No blocking issues. Safe to merge from a code-correctness standpoint.