fix(ci): use PAT for release checkout to bypass branch protection on formula push#35
Merged
seanseannery merged 1 commit intomainfrom Mar 7, 2026
Merged
Conversation
seanseannery
force-pushed
the
fix/release-homebrew-pr
branch
from
f563214 to
b99efd7
Compare
seanseannery
changed the title
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.
Key Changes
OPSFILE_RELEASE_PATtoken in the release job's checkout step so the Homebrew formula push to main can bypass branch protectionWhy do we need this?
Branch protection on
mainrequires changes go through a PR. The defaultGITHUB_TOKENdoesn't have permission to push directly. Using a PAT with Contents write access allows the release automation to push the formula update directly.New modules or other dependencies introduced
None — requires the
OPSFILE_RELEASE_PATrepo secret (already configured).How was this tested?
Will be validated on the next release dispatch.