ci: stop auto-releasing on TG develop publishes#112
Merged
Conversation
Now that Terminal.Gui supports clet from main, only trigger releases on tg-released (stable TG releases), not tg-develop-published. Route repository_dispatch to the main channel accordingly. Co-Authored-By: Claude Opus 4.6 (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.
Summary
tg-develop-publishedfromrepository_dispatchtriggers — only stable TG releases (tg-released) now trigger a clet releaserepository_dispatchto themainchannel (wasdevelop) since it now only fires for stable TG releasesWhy
Terminal.Gui now supports clet from
main, so there's no need to auto-release clet on every TG develop publish.Doc-update gate
No spec/decisions/runbook impact — CI-only change.
Test plan
🤖 Generated with Claude Code