Repository navigation
ci(release): retry the tap dispatch and say what to do when it fails - #2
Merged
Merged
Conversation
The tap job runs after the release is already published, so a failure there is not a build that did not happen -- it is a live tap pointing at the previous version while the README advertises this one. That is exactly what v1.0.0 did. Three attempts covers a transient API error. What it cannot fix is a token that is not allowed to dispatch, which is what actually happened, so the failure path now prints the ready-to-paste command and names the likely cause instead of leaving a red job with a bare 403 in it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.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
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.
The tap job runs after the release is published. A failure there is not "a build that did not happen" — it is a live tap pointing at the previous version while its README advertises this one. v1.0.0 did exactly that.
if: failure()step that prints the ready-to-pastegh workflow runcommand with the real version and checksum filled in, and names the likely cause. A bare403in a red job says nothing about what to do next.What retrying cannot fix is a token that is not permitted to dispatch, which is what actually happened —
TAP_TOKENstill returnsHTTP 403after three attempts at adjusting it, and the same 403 hit dotfix on 2026-09-22. The companion change is homebrew-tap#2, which verifies the artifact before committing so a failed bump leaves the tap on its previous working version.Not exercised yet: the failure path only runs on a real release, and
gh run rerunreplays the old workflow definition. The message rendering was checked locally; the retry loop is three lines around the unchanged command.🤖 Generated with Claude Code