Skip to content

Bump pinned Rust toolchain to 1.99.1 - #183

Open
wack-chores[bot] wants to merge 2 commits into
trunkfrom
update-to-rust-1.99.1
Open

wack-chores[bot] wants to merge 2 commits into
trunkfrom
update-to-rust-1.99.1

Conversation

@wack-chores

@wack-chores wack-chores Bot commented Oct 19, 2026

Copy link
Copy Markdown

Summary

  • Bumps rust-toolchain.toml from Rust 1.98.1 to 1.99.1 (latest stable, released 2026-10-13).
  • Bumps async-trait from 0.1.89 to 0.1.92 in Cargo.lock: 0.1.92 drops the #[must_use] attribute it used to inject onto desugared async-trait methods, which trips clippy's new double_must_use lint under 1.99 (17 errors across the trait definitions).

Verification

  • cargo make check-format ✅
  • cargo make clippy-flow ✅
  • cargo make clippy-jev ✅

🤖 Generated with Claude Code

wack chores and others added 2 commits October 19, 2026 11:05
Also bumps async-trait from 0.1.89 to 0.1.92, which drops the
`#[must_use]` injection that trips clippy's new double_must_use
lint under Rust 1.99.

Co-Authored-By: Claude Code <noreply@anthropic.com>
Update rust-toolchain.toml from 1.98.1 to the latest stable (1.99.1).
Rust 1.99 enables the double_must_use clippy lint, which fires inside
code generated by async-trait 0.1.89; bump async-trait to 0.1.92, which
resolves the lint in its generated code (dtolnay/async-trait#303).

Co-Authored-By: Claude Code <noreply@anthropic.com>
@wack-chores

wack-chores Bot commented Oct 26, 2026

Copy link
Copy Markdown
Author

Follow-up commit pushed (5688bf5): Cargo.toml now declares async-trait = "0.1.92" (the previous branch state only bumped the version in Cargo.lock, which cargo make clippy-flow's --locked invocations would have rejected). Re-verified cargo make check-format, cargo make clippy-flow, and cargo make clippy-jev on the full diff — all green.

🤖 Generated with Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants