Skip to content

chore: release v0.5.105 — ship pipeline auto-commit#320

Merged
githubrobbi merged 1 commit into
mainfrom
release/v0.5.105
May 29, 2026
Merged

chore: release v0.5.105 — ship pipeline auto-commit#320
githubrobbi merged 1 commit into
mainfrom
release/v0.5.105

Conversation

@githubrobbi
Copy link
Copy Markdown
Collaborator

Summary

just ship Phase 2 auto-commit for v0.5.105. Binaries + GitHub Release v0.5.105 are already live (step 09). This PR routes the corresponding commit through branch-protection rules.

Auto-merge

--auto --squash is queued — GitHub will merge as soon as the required status checks pass. Squash is required because main-protection mandates 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 satisfies required_signatures: true. The original author's signed commit remains verifiable in the PR branch history.

After merge

Local main had this commit with a different SHA before squash rewrote it onto main; recover with git fetch origin && git reset --hard origin/main.

@githubrobbi githubrobbi enabled auto-merge (squash) May 29, 2026 13:56
@githubrobbi githubrobbi merged commit d94117a into main May 29, 2026
22 checks passed
@githubrobbi githubrobbi deleted the release/v0.5.105 branch May 29, 2026 14: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