Cut Release: advance main via admin-merged PR - #35
Merged
Conversation
main is protected — the cut_release lane's direct push to main was rejected (PR + review + Unit Tests required). Advance main on a short-lived branch, open a PR, and admin-merge it instead. Requires a RELEASE_PAT secret (admin PAT) since the default GITHUB_TOKEN cannot bypass protection. Documents the secret and the manual PR flow in RELEASING.md. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
Changes
fastlane/Fastfile(cut_release): instead of direct-pushing themainversion bump, put it on achore/bump-main-<next>branch, open a PR, and admin-merge it (gh pr merge --squash --admin --delete-branch)..github/workflows/cut-release.yml: addpull-requests: write, and run the Cut step withGH_TOKEN: ${{ secrets.RELEASE_PAT }}.RELEASING.md: document theRELEASE_PATsecret and update the manual cut steps to advancemainvia a PR.Why
mainis a protected branch (changes must go through a PR; a review + the "Unit Tests" check are required). Thecut_releaselane's direct push tomainis rejected by that protection — the reason the last cut half-failed and needed a manual bump PR (#34). The defaultGITHUB_TOKENis write-only and cannot bypass protection, so an admin PAT is required to merge the bump PR. Admin-merge is safe here because the change is a single-lineMARKETING_VERSIONbump andenforce_adminsis off.Notes
RELEASE_PATrepo secret — a PAT owned by a repo admin withcontents: write+pull requests: write(or a classicrepo-scope token). Without it, the Cut Release workflow's admin-merge step will fail.