Use the release app for automatic Homebrew updates - #13
Merged
Merged
Conversation
bjarn
marked this pull request as ready for review
September 28, 2026 07:14
bjarn
enabled auto-merge (squash)
September 28, 2026 07:14
Bjornftw
self-requested a review
September 28, 2026 16:30
Bjornftw
approved these changes
Sep 28, 2026
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
2 participants
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.
Stable CLI releases currently use a personal token to open a Homebrew cask PR, then require a manual merge. Use the release app with a token restricted to homebrew-tap, and request an automatic squash merge after the tap checks pass.
Before requesting merge, check the PR source, target, changed file list, and exact cask content at its head commit. Bind the request to that commit. Retries reuse the existing PR and propagate merge-request failures. Keep the existing release and cask checks.
Validation: all 66 Python release-control tests passed, including 10 new Homebrew cases; actionlint and all GitHub CI checks passed. One Windows signing setup job passed after a retry. The app permissions and CLI release environment are configured. A live token test confirmed access to only homebrew-tap with Contents and Pull requests write permissions; the test token was revoked. A full stable-release run with the new workflow is still required after merge. Keep the old tap token for retries of older workflows.