Repository navigation
ci: add announce workflow for release discussions - #4071
Merged
Merged
Conversation
Creating the Announcements discussion needs GraphQL, which Claude Code sessions can't reach, so the release workflow guide left steps 10-11 manual. This dispatch-only workflow creates and closes the discussion with the Actions token, so a release session (or anyone) can trigger it with a title and body.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
This branch was successfully deployed
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.
Creating the Announcements discussion needs GraphQL, which Claude Code sessions can't reach (the API proxy serves REST only), so steps 10-11 of the release guide stayed manual. This adds a dispatch-only workflow that creates the discussion in the Announcements category and closes it right away (closed announcements still show pinned), using the Actions token. The run's summary links the created discussion.
With this merged, a release session can trigger the announcement itself and only the Discord post stays manual.
Generated by Claude Code