CI: auto-create GitHub release on version tags#4
Merged
Conversation
Add a tag-gated `release` job (needs: publish, contents: write) that extracts the matching section from CHANGELOG.md for the pushed v* tag and creates a GitHub release with it via the gh CLI. Falls back to a minimal note if the section isn't found. Future releases: push a v* tag and the pipeline publishes to NuGet and creates the GitHub release automatically. (v0.1.0's release was created manually, before this existed.) Co-Authored-By: Claude Opus 4.7 (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.
Adds a
releasejob to the CI workflow so future releases create their GitHub release automatically.Behaviour
v*tags (needs: publish), so it fires after the NuGet push succeeds.## [<version>] — …section fromCHANGELOG.mdfor the tag (e.g.v0.2.0→ the0.2.0block) and uses it as the release body; falls back to a minimal note if the section is missing.contents: writefor the release creation; uses the built-inGITHUB_TOKEN.Release flow going forward
main.git tag vX.Y.Z && git push origin vX.Y.Z.build→publish(NuGet) →release(GitHub release from the changelog section).v0.1.0's release was created manually since this automation didn't exist when that tag was pushed.🤖 Generated with Claude Code