Repository navigation
ci(ci): drop the one-release feat-as-patch rule - #63
Merged
Merged
Conversation
0.4.1 is out; feat commits release as minors again, per the angular preset. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
🎉 This PR is included in version 0.4.2 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
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.
Removes
{ "type": "feat", "release": "patch" }from.releaserc.json. It was added in #62 only so the distribution work would ship as 0.4.1, and 0.4.1 is now out. After this,featcommits release as minors again, per the angular preset. Thecicommit type triggers no release.Checks
pnpm lint: 0 errors..releaserc.jsonmatches what it was before Release: distribution — Claude Desktop extension, MCP Registry, plugin marketplace, clip doctor (v0.4.1) #62.