ci: auto-tag + publish a GitHub Release on version bump#7
Merged
Conversation
The v1.5.0 PR merged to main but no git tag or GitHub Release was ever created to mark it, unlike v1.4.0 / v1.4.1. Add a release workflow that, when the kit version in openapi.json (info.version, "v<x.y.z>") is not yet released, creates the tag — anchored to main's tip — and publishes a Release with notes drawn from the matching CHANGELOG.md section. The job is idempotent, runs on every push to main (so future version bumps self-tag), and is bootstrapped on the claude/** branch so the already-merged v1.5.0 gets its missing tag/Release. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NhzBUBpmFLVPAdBAJn8iAs
gsavastano
added a commit
that referenced
this pull request
Jun 20, 2026
The v1.5.0 PR merged to main but no git tag or GitHub Release was ever created to mark it, unlike v1.4.0 / v1.4.1. Add a release workflow that, when the kit version in openapi.json (info.version, "v<x.y.z>") is not yet released, creates the tag — anchored to main's tip — and publishes a Release with notes drawn from the matching CHANGELOG.md section. The job is idempotent, runs on every push to main (so future version bumps self-tag), and is bootstrapped on the introducing feature branch so the already-merged v1.5.0 gets its missing tag/Release.
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
2 participants
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.
The v1.5.0 PR merged to main but no git tag or GitHub Release was ever
created to mark it, unlike v1.4.0 / v1.4.1. Add a release workflow that,
when the kit version in openapi.json (info.version, "v<x.y.z>") is not yet
released, creates the tag — anchored to main's tip — and publishes a Release
with notes drawn from the matching CHANGELOG.md section. The job is
idempotent, runs on every push to main (so future version bumps self-tag),
and is bootstrapped on the claude/** branch so the already-merged v1.5.0
gets its missing tag/Release.