ci: release workflow — tag + publish on version bump - #11
Merged
Conversation
When package.json's version changes on main, tag vX.Y.Z on the merge commit and cut a GitHub release with auto-generated notes (contents: write, via the Actions GITHUB_TOKEN). Removes the manual gh release / tag-push step — tag pushes 403 from the dev sandbox, so cutting releases server-side in CI is the reliable path. Idempotent: no-ops if the tag already exists. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011GNDVjvsbTPsbWV9fEyjLt
bdelanghe
marked this pull request as ready for review
June 23, 2026 03:18
This was referenced Jun 23, 2026
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.
Automates release-cutting so future versions don't need the manual
gh release create/ tag-push dance (tag pushes 403 from the dev sandbox; this runs server-side in Actions).How it works
On push to
mainwhenpackage.jsonchanges, the job:versionfrompackage.json,vX.Y.Zis already tagged (idempotent — no-ops if so),gh release create vX.Y.Z --target <sha> --generate-notes.Uses
contents: write+ the defaultGITHUB_TOKEN; actions pinned by SHA to match the existing workflows.Flow from here
Bump
package.jsonin a PR → merge → this cuts the tag + release automatically.--generate-notesproduces a PR changelog; richer prose notes can still be edited in on the web after.Doesn't touch
v0.3.0(already released). First auto-cut will bev0.3.1/v0.4.0.🤖 Generated with Claude Code
Generated by Claude Code