fix: auto-approve automated version bump PRs - #7
Merged
Merged
Conversation
Bump PRs are authored by the PAT owner, who can't approve their own PRs, so the required review blocked every automated bump. Approve machine-generated bump PRs as github-actions[bot] instead, guarded to same-repo chore/bump-version-* branches whose diff is exactly the DESCRIPTION Version line. Human PRs still require a real review.
Derya
approved these changes
Aug 12, 2026
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
2 participants
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.
Follow-up to #4, replacing the abandoned GitHub App approach (#6). Bump PRs are authored by the PAT owner, who can't approve their own PRs — so the required review blocked every automated bump.
Changes
New
auto-approve-version-bump.yaml: approves machine-generated bump PRs asgithub-actions[bot], satisfying main's 1-review requirement so auto-merge can complete unattended.Guards — branch protection itself is untouched; every human PR still needs a real review:
chore/bump-version-*branches. Fork PRs get a read-onlyGITHUB_TOKENand can never approve, settings notwithstanding.Version:line of DESCRIPTION — a code change smuggled onto a bump branch gets no approval.Deployment notes
fix:-typed, so merging it re-triggers the version bump (PR chore: bump version to 0.1.1 #5 was closed) and exercises the full chain: bump PR → bot approval → auto-merge →v0.1.1tag.🤖 Generated with Claude Code