Skip to content

fix: route version-bump commit through PR to satisfy branch protection#9

Merged
TMHSDigital merged 1 commit into
mainfrom
fix/release-use-pr
May 24, 2026
Merged

fix: route version-bump commit through PR to satisfy branch protection#9
TMHSDigital merged 1 commit into
mainfrom
fix/release-use-pr

Conversation

@TMHSDigital
Copy link
Copy Markdown
Owner

Root cause

The release workflow was trying to push directly to main with
git push origin main, which the repository ruleset rejects
because all changes must go through a pull request and the
Ecosystem drift check status is required.

The bypass-actor API also rejected adding github-actions[bot]
because it requires an organization context (personal repo).

Fix

The version-bump step now:

  1. Creates branch chore/release-vX.Y.Z
  2. Commits version files there
  3. Opens a PR
  4. Polls until the Ecosystem drift check passes (max 5 min)
  5. Squash-merges the PR and deletes the branch
  6. Re-syncs local git state to merged main before tagging

No behaviour change for the tag and release creation steps.

Main requires PRs and the drift-check status check; the previous direct
push to main was rejected by the repository ruleset. The release workflow
now creates a chore/release-vX.Y.Z branch, opens a PR, polls for the
drift check to pass, merges, then re-syncs git state before tagging.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Signed-off-by: fOuttaMyPaint <TMhospitalitystrategies@gmail.com>
@github-actions github-actions Bot added the ci label May 24, 2026
@TMHSDigital TMHSDigital merged commit 01bf0b8 into main May 24, 2026
7 checks passed
@TMHSDigital TMHSDigital deleted the fix/release-use-pr branch May 24, 2026 20:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant