Repository navigation
fix(release): open a homebrew-tap PR instead of pushing - #49
Draft
adolsalamanca wants to merge 1 commit into
Draft
adolsalamanca wants to merge 1 commit into
adolsalamanca wants to merge 1 commit into
Conversation
- homebrew-tap main now needs a pull request with one approval, so a direct push from the release fails
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
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.
This change adds
homebrew_casks[].repository.pull_requestto.goreleaser.yaml, so the release opens a pull request on timescale/homebrew-tap instead of pushing the cask tomain. Since 2026-11-12, therequire-prruleset protects the tap'smain. It requires a pull request with one approval given after the last push, and no account can bypass it. A direct push tomainfails.The config sets no
branch, so GoReleaser pushes the cask to aghost-<version>branch and opens a ready pull request againstmain. The account that ownsHOMEBREW_TAP_GITHUB_TOKENpushes the branch, so each release needs an approval from a different account. Auto-merge can be enabled on that pull request. The tap does not delete merged branches.refs: PLA-2133