docs(release): require explicit --title and re-run notify-tap on edits#218
Merged
github-actions[bot] merged 1 commit intomainfrom Apr 19, 2026
Merged
docs(release): require explicit --title and re-run notify-tap on edits#218github-actions[bot] merged 1 commit intomainfrom
--title and re-run notify-tap on edits#218github-actions[bot] merged 1 commit intomainfrom
Conversation
`notify-tap` validates the GitHub Release title against `fusionAIze Gate vX.Y.Z`. Some `gh` versions default the title to just the tag name when only `--notes-from-tag` is given, which silently breaks the Homebrew tap dispatch — v2.3.0 hit this twice today. - RELEASES.md and docs/PUBLISHING.md now explicitly call out the `--title "fusionAIze Gate vX.Y.Z"` flag and document that a `gh release edit --title` after the fact will re-trigger the workflow. - scripts/faigate-release surfaces the full `gh release create` command in its next-steps output, with a test that locks in the convention. - .github/workflows/notify-tap.yml now also runs on `release: edited`, so a title fix unblocks the dispatch without delete + recreate. - .github/RELEASE_TEMPLATE.md adds the title shape to the checklist. Co-Authored-By: Claude Opus 4.7 <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.
Summary
notify-tapvalidates the GitHub Release title againstfusionAIze Gate vX.Y.Z. Someghversions default the title to just the tag name (vX.Y.Z) when only--notes-from-tagis given, which silently breaks the Homebrew tap dispatch. The v2.3.0 release tripped this twice today.RELEASES.md,docs/PUBLISHING.md,.github/RELEASE_TEMPLATE.md) now explicitly require the--titleflag, andscripts/faigate-releasesurfaces the fullgh release createcommand in its next-steps output with a test that locks in the convention..github/workflows/notify-tap.ymlnow also runs onrelease: edited, so agh release edit --titleafter the fact unblocks the dispatch without needing a delete + recreate.Test plan
pytest tests/test_release_scripts.py(all 6 pass, including the new title-shape assertion)pytest -qrun — pre-existing 13ruamel-import failures intest_dashboard_settings.py/test_metrics_traces.pyare unrelated to this changegh release createrenders the fullfusionAIze Gate vX.Y.Ztitle and thatnotify-tapdispatches on first tryeditedtrigger fires the dispatch retroactively🤖 Generated with Claude Code