Skip to content

Release on a version tag instead of a commit message - #26

Merged
steckes merged 2 commits into
mainfrom
ci/release-on-tag
Sep 7, 2026
Merged

steckes merged 2 commits into
mainfrom
ci/release-on-tag

Conversation

@steckes

@steckes steckes commented Sep 7, 2026

Copy link
Copy Markdown
Contributor

No description provided.

steckes and others added 2 commits September 7, 2026 22:38
Publishing was gated on the message of the commit pushed to main matching a version
number, with all tags ignored. That only works when the release commit is the version
bump itself; the 0.24.0 bump landed inside the rewrite PR, so there was no way left to
trigger a release short of an artificial commit.

Trigger on `x.y.z` and `vx.y.z` tags and run `publish` only for those. The tag is checked
against package.json before publishing, since npm takes the version from there and a
mismatch would ship something other than what was tagged.

`paths-ignore` is dropped rather than kept: GitHub evaluates path filters for tag pushes
too, and a tag on a commit already pushed to main carries no changed files, so the filter
would skip the release run.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@steckes
steckes merged commit 1086952 into main Sep 7, 2026
@steckes
steckes deleted the ci/release-on-tag branch September 7, 2026 20:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant