Skip to content

chore(deps): bump async-trait so fmt + clippy passes on stable 1.99 - #98

Merged
adbarc92 merged 1 commit into
mainfrom
fix/ci-clippy-double-must-use
Oct 10, 2026
Merged

adbarc92 merged 1 commit into
mainfrom
fix/ci-clippy-double-must-use

Conversation

@adbarc92

Copy link
Copy Markdown
Owner

fmt + clippy has been red on main and on every branch since 2026-10-01, including the docs-only #96 and #97.

Cause

CI installs stable Rust unpinned. Clippy 1.99 added double_must_use cases that fire on the #[must_use] async-trait 0.1.89 puts on its generated methods, so all four #[async_trait] traits in fleetd (DocSource, Forge, Planner, Runner) fail under -D warnings. No source in this repo changed.

Fix

cargo update -p async-trait: 0.1.89 -> 0.1.92 in the root Cargo.lock. It brings in syn 3.0.5 as a build dependency of the macro. No source changes.

Verification

CI on this branch: fmt + clippy passes, both the root workspace and cockpit/ui/src-tauri clippy steps. Not reproduced locally, since the local toolchain is 1.93 and does not have the lint.

Not in this PR

The toolchain is still unpinned, so the next stable release can do this again. Pinning it is a separate decision, and it is related to #95.

…st_use

Stable clippy (1.99) rejects the #[must_use] that async-trait 0.1.89 emits on its generated methods, failing fmt + clippy on main and every branch since 2026-10-01.
@adbarc92
adbarc92 merged commit e31891a into main Oct 10, 2026
18 checks passed
@adbarc92
adbarc92 deleted the fix/ci-clippy-double-must-use branch October 10, 2026 18:10
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.

1 participant