chore: release v0.6.30 — ship pipeline auto-commit#581
Merged
Conversation
The version banner's rerun trigger watched only .git/HEAD — but a pull, commit, or reset onto the *current* branch leaves HEAD's symref line unchanged, so the embedded commit SHA went stale and --version reported the previous build's commit: exactly the 'am I running the fix?' trap the stamp exists to prevent. .git/logs/HEAD (the reflog) appends on every HEAD movement, making it the reliable trigger; .git/HEAD stays watched for branch switches on fresh clones without a reflog entry yet. Ported from the uffs-products build flow, where the same gap was found and fixed first.
githubrobbi
enabled auto-merge
July 23, 2026 15:29
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.6.30 — the[workspace.package].versionbump inCargo.toml. This PR routes that commit through branch-protection rules. Once it merges tomain, runjust release-tagto cut the signedv0.6.30tag, which firesrelease.ymland builds the cross-platform binaries + GitHub Release v0.6.30. (No auto-tag on merge — the tag step is manual on-demand, Path B.)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.6.30, so localmainnever drifted — sync it with a plaingit pull --ff-only origin main(noreset --hardneeded).