Fix: Make auto-release resilient to homebrew tap failures#380
Merged
Conversation
- Remove pull_request config from goreleaser brews (token lacks fork permissions, causing 404 on repos// URL) - Add continue-on-error to goreleaser step so homebrew failures don't block the release - Add post-release verification step that checks the GitHub release exists and only fails if the actual release wasn't published Co-authored-by: Cursor <cursoragent@cursor.com>
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
pull_requestconfig from brews (theHOMEBREW_TAP_GITHUB_TOKENlacks fork permissions, causing404 repos//errors)continue-on-error: trueto the goreleaser step so homebrew tap push failures don't block the releaseContext
The
giantswarm/homebrew-musterrepo has branch protection requiring PRs. The goreleaserpull_request.enabledfeature tried to fork the repo but the token couldn't determine the authenticated user's fork (empty owner/repo in API calls).Since the homebrew tap update is non-critical (release artifacts are published fine), this makes it non-blocking while logging a warning.
Test plan
Made with Cursor