chore: release v0.5.106 — ship pipeline auto-commit#323
Merged
Conversation
…uration expects) nightly-2026-05-31 clippy splits unused_async: inherent async-no-await methods now fire BOTH clippy::unused_async and clippy::unused_async_trait_impl, while trait-impl methods (rmcp ServerHandler in uffs-mcp) fire only the trait variant. Update the uffs-mft non-windows stub expects to cover both lints; keep uffs-mcp on the single trait lint. Signatures (async, &self, by-value callback) are kept for cross-cfg API parity. duration_suboptimal_units no longer fires on Duration::from_secs(120)/from_secs(300), so those #[expect] attrs were unfulfilled (-D warnings). Remove the stale expects in uffs-cli and uffs-daemon. Also correct the rust-toolchain.toml pin comment (05-20 -> 05-31).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
just shipPhase 2 auto-commit for v0.5.106 — the[workspace.package].versionbump inCargo.toml. This PR routes that commit through branch-protection rules. Once it merges tomain,auto-tag-release.ymltags the commit and invokesrelease.yml, which builds the cross-platform binaries and publishes GitHub Release v0.5.106.Auto-merge
--auto --squashis queued — GitHub will merge as soon as the required status checks pass. Squash is required becausemain-protectionmandates signed commits, and GitHub's rebase-auto-merge cannot sign the rebased commit; the squash-merge commit is signed by GitHub's own key, which satisfiesrequired_signatures: true. The original author's signed commit remains verifiable in the PR branch history.After merge
The auto-commit lived only on
release/v0.5.106, so localmainnever drifted — sync it with a plaingit pull --ff-only origin main(noreset --hardneeded).