ci: fix the bump → publish chain (auto-label PAT + drop homebrew/core tap)#9
Merged
Conversation
GitHub's recursion guard: a label applied with the default GITHUB_TOKEN does not fire downstream workflows. publish.yml listens on pull_request_target.labeled, so without a PAT the chain stalls after auto-label. Reuses the existing BUMP_PR_PAT secret. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
csparker247
changed the title
1 task
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.
Summary
auto-label.yml: useBUMP_PR_PATso the applied label actually firespublish.yml.publish.yml: drop the obsoletebrew tap Homebrew/corecall.Why
auto-label.yml — GitHub's recursion guard means labels applied with
GITHUB_TOKENdo not fire downstream workflows.publish.ymllistens onpull_request_target.labeled, so without a PAT the chain stalls at the label step. Observed on #8.publish.yml — modern Homebrew treats
homebrew/coreas an API-only tap and rejectsbrew tap homebrew/corewithout--force.brew pr-pulldoesn't need it tapped. Observed on the first publish attempt for #8.Test plan
pr-pulllabel on openabf: revision 1 #8 —publish.ymlshould fire and complete.repository_dispatch) should complete the full chain end-to-end with no human intervention.🤖 Generated with Claude Code