Repository navigation
docs: describe the announcement-file flow in the release guide - #4074
Merged
Merged
Conversation
Step 10 documented the GraphQL mutations, which release sessions can't run. Point it at the Announce Release workflow instead: commit a file under .github/announcements and merge.
|
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.
Step 10 of the release guide documented the GraphQL mutations, which release sessions can't run (and workflow dispatch is also unavailable to them). Point it at the flow that works everywhere: commit a markdown file under
.github/announcements/and merge; the Announce Release workflow from #4072 creates and closes the discussion. Used successfully for the v2.5.0 announcement (#4073).Generated by Claude Code