Update async-trait to 0.1.92 for clippy 1.99
async-trait 0.1.92 stops emitting #[must_use] on trait methods that return a boxed future. Stable clippy 1.99 rejects that attribute under -D warnings (double_must_use), which fails cargo-build-and-test on main and every open PR at crates/relayburn-cli/src/harnesses/mod.rs:124.
Lockfile-only change (cargo update -p async-trait).
Verified: clippy --workspace --all-targets -D warnings fails on main with Rust 1.99.0 and passes with this change on 1.99.0 and 1.95.0; cargo test --workspace passes on 1.99.0.
🤖 Generated with Claude Code
[!NOTE]
Low Risk
Dependency lockfile refresh with no runtime code changes; intended to fix CI/clippy on Rust 1.99.
Overview
Lockfile-only bump of async-trait from 0.1.89 to 0.1.92 via cargo update -p async-trait. The lockfile also records syn 3.0.6 (pulled in by the new async-trait) and pins many macro crates to syn 2.0.117 explicitly.
0.1.92 stops putting #[must_use] on async trait methods that return a boxed future. On Rust/clippy 1.99 with -D warnings, the old attribute triggers double_must_use and breaks workspace clippy (e.g. around #[async_trait] on HarnessAdapter in crates/relayburn-cli/src/harnesses/mod.rs). No application source changes—only Cargo.lock.
Reviewed by Cursor Bugbot for commit 0b46627f4c59d7213902e2a9f49b3e86cc04f243. Bugbot is set up for automated code reviews on this repo. Configure here.