Skip to content

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

Closed
yultyyev wants to merge 1 commit into
mainfrom
ci/drop-feat-patch-rule
Closed

yultyyev wants to merge 1 commit into
mainfrom
ci/drop-feat-patch-rule

Conversation

@yultyyev

Copy link
Copy Markdown
Collaborator

What

Removes { "type": "feat", "release": "patch" } from releaseRules in .releaserc.json.

Why

The rule was there only so the shorts work (#73, #78, #85, #86) released as a patch, v0.5.2, as decided in the shorts plan. 0.5.2 is out, so feat commits go back to releasing as minors under the angular preset. The same thing was done after 0.4.1 (#63).

This is a ci commit, so merging it releases nothing.

Checks

  • .releaserc.json parses as JSON, and pnpm lint is clean (7 pre-existing warnings).
  • v0.5.2 verified before opening this:
    • the release run is green;
    • npm latest is 0.5.2, with provenance;
    • makemyclip-editor.mcpb is on the GitHub release;
    • the MCP Registry lists 0.5.2 as latest.
  • Codex review: no findings. It noted that the dependency and security patch rules stay intact.

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

Copy link
Copy Markdown
Collaborator Author

Duplicate of #88 (same one-line change, opened 16 s earlier by the shorts session).

@yultyyev yultyyev closed this Nov 16, 2026
@yultyyev
yultyyev deleted the ci/drop-feat-patch-rule branch November 16, 2026 04:46
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