Skip to content

ci(ci): drop the one-release feat-as-patch rule - #88

Merged
yultyyev merged 1 commit into
mainfrom
ci/drop-patch-rule-0.5.2
Nov 16, 2026
Merged

yultyyev merged 1 commit into
mainfrom
ci/drop-patch-rule-0.5.2

Conversation

@yultyyev

Copy link
Copy Markdown
Collaborator

0.5.2 is out (release workflow green, npm latest = 0.5.2, .mcpb on the GitHub release, MCP Registry lists 0.5.2). This removes { "type": "feat", "release": "patch" } from .releaserc.json, added for that release in #87, so feat commits release as minors again per the angular preset. Same as #63 did after 0.4.1.

Checks

  • @semantic-release/commit-analyzer with the new config: feat → minor, fix → patch, chore(deps) → patch, docs → no release.
  • biome check .releaserc.json: clean.
  • Codex review: no findings.

Merging this releases nothing: a ci commit isn't a release type.

0.5.2 is out; feat commits release as minors again, per the angular
preset.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@yultyyev
yultyyev merged commit e090b42 into main Nov 16, 2026
1 check passed
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