publish: create a GitHub release after each npm publish - #122
Merged
Merged
Conversation
Every successful npm publish now also tags v<version> and creates a GitHub release with auto-generated notes, so watchers and stargazers are notified. Requires contents: write; the v0.0.17 release was created manually and serves as the baseline tag for generated notes. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The Default CI job hung twice today on master pushes (the intermittent install hang known from #115), each time blocking as in_progress toward GitHub's 6-hour default timeout. Healthy runs finish in under 10 minutes; a 30-minute cap turns a hang into a visible failure that can simply be rerun. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Owner
Author
|
Added a second commit: all CI and publish jobs now have |
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
Makes GitHub releases part of the release routine: after a successful
npm publish, the publish workflow now runsgh release create "v$NEWVERSION" --generate-notes, tagging the released commit and notifying watchers/stargazers.permissions.contentsraised fromreadtowrite(needed to create the tag + release; provenance still usesid-token: write).GH_TOKENprovided to the step fromgithub.tokenfor theghCLI.Merging this PR does not publish or release anything (version is unchanged); the routine takes effect on the next version bump.
🤖 Generated with Claude Code