semantic-release / semantic-release/commit-analyzer
How to make sure NO Major release is triggered?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 448
- Forks
- 82
- Avg merge
- 17h 41m
- Merged PRs (30d)
- 4
Description
Hello!
I need to make sure that whatever commit message is there won't be a MAJOR release.
Currently with default angular preset all that is needed is BREAKING CHANGE: in the commit message footer to trigger a MAJOR release.
For now I just associate breaking changes with a minor release which is fine for our use case and it results in just a MINOR version upgrade.
plugins: [
[
"@semantic-release/commit-analyzer",
{ releaseRules: [{ breaking: true, release: "minor" }] },
],
],
Question - is there a more correct solution ?
Thank you
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the @semantic-release/commit-analyzer configuration entry point and its releaseRules handling; compare the angular preset's BREAKING CHANGE behavior with the requested major-release suppression. Done means identifying and documenting or testing a configuration path that prevents major releases while preserving the stated minor-release behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- release
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100