chore: replace release-npm-action with simple release script#100
Merged
chore: replace release-npm-action with simple release script#100
Conversation
Coverage Report
File CoverageNo changed files found. |
Replace tobua/release-npm-action with an inline release script that always publishes on merge to main. Version bump is determined from commits since the last tag: - BREAKING CHANGE in body → major - feat: prefix → minor - everything else (fix, chore, docs, untagged) → patch Skips release if HEAD is already tagged to prevent duplicates. Creates a git tag and GitHub release with auto-generated notes. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
rohal12
force-pushed
the
chore/always-release-on-merge
branch
from
35203c1 to
cc6e63a
Compare
rohal12
changed the title
rohal12
pushed a commit
that referenced
this pull request
Mar 22, 2026
The previous grep pattern matched "BREAKING CHANGE" anywhere in commit bodies, which false-positived on the PR #100 commit that mentioned the phrase in a bullet point describing the release rules. Now requires either: - "BREAKING CHANGE: " at the start of a line (conventional footer) - "type!: " pattern in the commit subject (e.g., "feat!: drop v1 API") Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
rohal12
pushed a commit
that referenced
this pull request
Mar 22, 2026
The previous grep pattern matched "BREAKING CHANGE" anywhere in commit bodies, which false-positived on the PR #100 commit that mentioned the phrase in a bullet point describing the release rules. Now requires either: - "BREAKING CHANGE: " at the start of a line (conventional footer) - "type!: " pattern in the commit subject (e.g., "feat!: drop v1 API") Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2 tasks
rohal12
added a commit
that referenced
this pull request
Mar 22, 2026
## Summary Two fixes that were pushed to the #100 branch after it was already merged: - **Fix major-bump false positive**: Require `BREAKING CHANGE: ` at start of line (conventional footer) or `type!: ` in commit subject — no longer matches the phrase mentioned casually in commit bodies (which caused the accidental v1.0.0) - **Version preview workflow**: Comments on PRs with the predicted version on open/push/title edit, e.g. "merging this PR will publish **v0.32.1** (patch bump from v0.32.0)". Updates the same comment instead of creating duplicates. ## Test plan - [ ] This PR itself should get a version preview comment predicting v0.32.1 - [ ] Merging should publish v0.32.1 (patch, not major) 🤖 Generated with [Claude Code](https://claude.com/claude-code)
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.
Summary
Replace
tobua/release-npm-actionwith an inline release script that always publishes on every merge to main, regardless of commit message format.Version bump is determined from commits since the last git tag:
BREAKING CHANGEin commit body → majorfeat:prefix → minorfix:,chore:,docs:, untagged, merge commits) → patchOther details:
vX.Y.Z) and GitHub release with auto-generated notesactions/setup-nodewithregistry-urlfor npm authtobua/release-npm-actionTest plan
feat:PR → verify minor version bump + npm publishchore:PR → verify patch version bump + npm publish🤖 Generated with Claude Code