chore(npm): tag and cut a GitHub Release on publish - #33
Merged
Conversation
grunt bump already commits and tags vX.Y.Z locally, but pushing that tag was a manual step and no GitHub Release was ever created. Add a postpublish hook that runs only after npm publish succeeds: it pushes the branch with --follow-tags (bump's tags are annotated, so they travel), then creates the Release with auto-generated notes. --verify-tag makes gh abort instead of inventing a tag at HEAD if you published without bumping first. Requires the GitHub CLI, authenticated; documented along with the rest of the release flow in the README. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
📦 PR Preview deployed! Examples are available at: |
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.
grunt bump already commits and tags vX.Y.Z locally, but pushing that tag was a manual step and no GitHub Release was ever created. Add a postpublish hook that runs only after npm publish succeeds: it pushes the branch with --follow-tags (bump's tags are annotated, so they travel), then creates the Release with auto-generated notes.
--verify-tag makes gh abort instead of inventing a tag at HEAD if you published without bumping first. Requires the GitHub CLI, authenticated; documented along with the rest of the release flow in the README.