ci: auto-create GitHub Release with generated notes after publish#8
Merged
Conversation
Add a github-release job (needs: publish) that runs `gh release create` with --generate-notes, so every published tag gets a GitHub Release whose notes are built from the PRs merged since the previous release. Uses the runner's preinstalled gh (no third-party action) and contents: write only on this job, keeping the publish job least-privilege. Co-Authored-By: Claude Opus 4.8 (1M context) <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
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.
Releases stopped being created after
v0.3.0, even though tags/npm publishes continued. This adds agithub-releasejob to the publish workflow so each release is recorded automatically.What
github-releasejob,needs: publish(only runs after a successful npm publish).gh—gh release create "$GITHUB_REF_NAME" --generate-notes --latest --verify-tag— so no third-party action is introduced.--generate-notesbuilds "What's Changed" from the PRs merged since the previous release; going forward each release's notes are scoped to just its changes.contents: writeis scoped to this job only;publishkeeps its minimalcontents: read+id-token: write.Note
v0.5.0was backfilled manually (it published before this existed): https://github.com/Tokenbooks/wt/releases/tag/v0.5.0🤖 Generated with Claude Code