Publish GitHub Releases with changes between tags#2
Merged
Conversation
Pushing a vX.Y.Z tag now triggers a release workflow that gates on go vet + go test -race, then publishes a GitHub Release. The body lists every non-merge commit since the previous v* tag plus a compare link, so each release shows exactly what changed between versions. scripts/release-notes.sh generates the notes and is locally runnable for previewing a release body before tagging. 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
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
Adds a release workflow so that publishing a version on GitHub shows the changes between the two versions.
.github/workflows/release.yml— triggers on pushing av*tag (matches the existinggit tag vX.Y.Z && git push --tagsflow). It re-runsgo vet ./...andgo test -race ./...against the tagged commit as a pre-publish gate, then creates a GitHub Release viagh release create --verify-tag.scripts/release-notes.sh— generates the release body: every non-merge commit since the previousv*tag (- subject (shortSHA), auto-linkified by GitHub) plus acompare/<prev>...<new>link. Locally runnable to preview a release before tagging:bash scripts/release-notes.sh vX.Y.Z.CHANGELOG.md— documents that pushing a tag now auto-publishes the release, and how to preview notes locally.Example release body
Notes
commits/<tag>link), the no-changes case, and a missing-tag error.fetch-depth: 0is set so the workflow has full history/tags to diff against.release.ymlmust land onmainfirst; tags pushed afterward will trigger it.Verification
bash -nsyntax check + valid YAML parse.scripts/release-notes.shagainst the existingv0.1.0andv0.1.1tags — correct diff ranges, compare links, andgit@-remote →owner/repoparsing.🤖 Generated with Claude Code