Repository navigation
Create the GitHub release as a draft - #94
Merged
Merged
Conversation
Public release notes are reviewed and published manually; npm publishing is unchanged. Co-Authored-By: Claude Fable 5.1 <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
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.
What it does
On a version tag, the GitHub release is created as a draft with a one-line body instead of a published release with auto-generated commit notes. npm publishing is unchanged. Public release notes are written, reviewed and published manually.
How to test it
X.Y.Zrelease appears.Acceptance criteria
Link to ticket
https://trello.com/c/ywKiYIhs
🤖 Generated with Claude Code