semantic-release / semantic-release/commit-analyzer
Uppercase scope not triggering a release (anymore)
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 448
- Forks
- 82
- Avg merge
- 17h 41m
- Merged PRs (30d)
- 4
Description
Hi,
I just updated to semantic-release 23 and now a release is not triggered anymore if I add an uppercase scope to my commit-message. It used to work fine in version 22.
Sadly I can not find any configuration or option to allow for a casing-option.
feat(ABC): my new feature used to trigger a new release in my pipeline but it does not anymore. However feat(abc): my new feature does.
Any idea how I can fix this?
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 reproducing the reported behavior with semantic-release 23 using feat(ABC): my new feature and feat(abc): my new feature, then trace how commit scopes are parsed and analyzed. Done means uppercase scopes trigger the same release as lowercase scopes, with a regression test covering both cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100