chore: drop the unused "feature" changelog type from release config - #27
Merged
Conversation
`feature` is not a valid @commitlint/config-conventional type, so a `feature:` commit can never pass the Verify Commits workflow — the release-notes-generator mapping for it is dead config that contradicts our commitlint rules. Drop it and rely on the standard `feat` type. Mirrors the same cleanup in @harperfast/nextjs. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
|
🎉 This PR is included in version 1.1.4 🎉 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
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.
Removes the
{ "type": "feature", "section": "Features" }mapping from.releaserc.json.featureis not a valid@commitlint/config-conventionaltype, so afeature:commit can never pass the Verify Commits workflow. That makes the release-notes-generator mapping for it dead config that contradicts our own commitlint rules — it can never actually categorize a commit. Dropping it and relying on the standardfeattype keeps the release config consistent with what commitlint allows.Flagged by automated review on HarperFast/nextjs#54; applying the same cleanup here so the two plugins' release configs stay in sync.
No behavior change (the mapping never fired).
🤖 Generated with Claude Code