Repository navigation
fix(release): publish automatically when a version bump merges to main - #5
Merged
Merged
Conversation
release.yml only ran on `v*` tag pushes, so merging #4 (0.1.6) released nothing: no one pushed the tag. Now a push to main that changes package.json publishes when `v<version>` is not yet tagged, and the release job creates the tag. Manual tag pushes still work. Publish and release skip work already done, so re-runs are safe.
a-tokyo
force-pushed
the
ci/auto-release-on-merge
branch
from
October 19, 2026 14:44
91433bf to
39a7679
Compare
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.
Why
Merging #4 bumped the version to 0.1.6 but nothing was published.
release.ymlonly triggered onv*tag pushes, and no tag was pushed. Only CI ran.What
release.ymlalso runs on pushes tomainthat touchpackage.jsonor the workflow, plusworkflow_dispatch.checkjob: on a tag push, verifies the tag matchespackage.json. Onmain, releases only ifv<version>is not tagged yet.publishskipsnpm publishif the version is already on npm.releaseskips if the GitHub Release exists and creates the tag otherwise (via--target $GITHUB_SHA). Re-runs are safe.Merging this ships 0.1.6
This PR edits
release.yml, so its merge triggers the workflow onmain.v0.1.6does not exist yet, so it publishes 0.1.6 and creates the release.Vulnerabilities
One open alert left:
bracesGHSA-vfj7-8cjw-p6xm (via@next/eslint-plugin-next→fast-glob@3.3.1→micromatch→braces@3.0.3). Everybracesversion is affected and no patch exists, so there is nothing to bump.npm audit fixsuggests a downgrade to@next/eslint-plugin-next@14, which is wrong.🤖 Generated with Claude Code