Skip to content

release: open a homebrew-tap PR instead of direct-pushing#27

Merged
stxkxs merged 1 commit into
mainfrom
goreleaser-tap-pr-mode
Jun 6, 2026
Merged

release: open a homebrew-tap PR instead of direct-pushing#27
stxkxs merged 1 commit into
mainfrom
goreleaser-tap-pr-mode

Conversation

@stxkxs

@stxkxs stxkxs commented Jun 6, 2026

Copy link
Copy Markdown
Member

homebrew-tap's main is branch-protected (requires a PR), so goreleaser's default direct push to the tap is rejected even with a valid token — the reason the v1.0.0 and v2.0.0 release runs both failed the brew step (I published v2.0.0's formula by hand via a PR). Enabling brews.repository.pull_request makes goreleaser open a formula PR that satisfies the protection.

Pairs with the owner restoring HOMEBREW_TAP_GITHUB_TOKEN's write access to the tap (the expired key). With both in place, future vX.Y.Z tags publish the formula automatically via a PR. goreleaser check passes.

Note (not addressed here): goreleaser flags brews as deprecated in favor of homebrew_casks — a separate future migration.

homebrew-tap's main is branch-protected (requires a PR), so goreleaser's default
direct push is rejected even with a valid token — which is why the v1.0.0 and
v2.0.0 release runs failed the brew step (I published v2.0.0's formula by hand via
a PR). Enable brews.repository.pull_request so the release opens a formula PR that
satisfies the protection. Pairs with restoring the HOMEBREW_TAP_GITHUB_TOKEN's
write access to the tap (owner). goreleaser check passes.
@stxkxs stxkxs merged commit b299004 into main Jun 6, 2026
4 checks passed
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