Skip to content

ci(release): merge the homebrew tap bump PR automatically#46

Merged
ch99q merged 1 commit into
mainfrom
ci/auto-merge-tap-bump
Jul 7, 2026
Merged

ci(release): merge the homebrew tap bump PR automatically#46
ch99q merged 1 commit into
mainfrom
ci/auto-merge-tap-bump

Conversation

@ch99q

@ch99q ch99q commented Jul 7, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • The bump-homebrew release job opened a tap PR but left merging manual, and that step gets forgotten — the 0.5.0 bump PR sat unmerged for two months (v0.7.0's needed a manual merge today).
  • The tap has no CI or branch protection, so the job now merges the PR immediately after opening it; the PR remains as an audit trail, and the bump branch is deleted afterwards.
  • No new token permissions needed: HOMEBREW_TAP_TOKEN already has contents: write + pull-requests: write, which covers squash-merging.

Test plan

  • vp test — unaffected (workflow-only change; suite passed on this base earlier today)
  • vp lint — workflow YAML is outside lint scope; vp check clean repo-wide
  • Manual: verified the tap repo has no branch protection or checks (gh api .../branches/mainprotected: false, no checks on bump branches), and exercised the identical gh pr merge --squash against tap PR ci: add cross-platform check and binary build pipeline #4 for v0.7.0 with the same permission set

The bump job only opened the PR, leaving the merge as a manual step
that gets forgotten (the 0.5.0 bump was never merged). The tap has no
CI or branch protection, so merge the PR right after opening it; it
remains as an audit trail. Needs no new token permissions.
@ch99q ch99q merged commit 11e4b93 into main Jul 7, 2026
4 checks passed
@ch99q ch99q deleted the ci/auto-merge-tap-bump branch July 7, 2026 18:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant