semantic-release / semantic-release/commit-analyzer
Allow limiting release type <= type
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 448
- Forks
- 82
- Avg merge
- 17h 41m
- Merged PRs (30d)
- 4
Description
I have a package which is based upon a parent package. If parent is x.y.z and the child package is a.b.c, I would like to enforce x.y == a.b. I believe I can do this by overriding all of the default rules with:
{type: 'feat', release: 'patch'},
{type: 'fix', release: 'patch'},
...
{tag: 'Breaking', release: 'patch'},
However this is fragile and depends on overriding all default rules. I propose a maxReleaseType or similar configuration option.
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 by locating the configuration handling for the default release rules and the proposed maxReleaseType option. Trace how commit types and tags are converted into release levels, then define completion as enforcing an upper release-type limit without requiring every default rule to be overridden.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100