ci(release): notify the Homebrew tap when the Release workflow completes - #22
Merged
Merged
Conversation
The GitHub Release is created with GITHUB_TOKEN, whose events do not start workflows, so release: published never fired and the tap only caught 1.6.0 on its poll. Follow the Release workflow's completion instead. Co-Authored-By: Claude Opus 5.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
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.
cargo-dist creates the GitHub Release with
GITHUB_TOKEN, and events made with that token don't start other workflows, sonotify-tapnever ran for 1.6.0 (I dispatched it by hand). This PR triggers it onworkflow_runofReleaseinstead, only for successful tag-push runs.🤖 Generated with Claude Code