commit-analyzer

commit-analyzer copied to clipboard

Fixes https://github.com/semantic-release/commit-analyzer/issues/231

xakraz

Unexpected major release because commit description includes a line starting with "Breaking change"

1

It's possible there isn't a reasonable way to avoid this, but I recently encountered an issue where a commit message triggered a unexpected major release for me. ```diff diff --git...

brian-smith-tcril

Exclamation mark (!) after type/scope completely ignores commit

9

I'm using the following config: ```js module.exports = { branches: ['master', 'test_commit'], repositoryUrl: 'ssh://git@*********', plugins: [ [ '@semantic-release/commit-analyzer', { preset: 'conventionalcommits' } ], '@semantic-release/release-notes-generator', '@semantic-release/changelog', '@semantic-release/npm', [ '@semantic-release/git', { message:...

dimitrisfasoulas

How to make sure NO Major release is triggered?

1

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...

depressedPlumber502

releaseRules overriding if is a major version

6

The following scenario is not working properly **Version** `[email protected]` **Config** ```js //.releaserc.mjs const config = { branches: ['main'], preset: 'conventionalcommits', plugins: [ [ '@semantic-release/commit-analyzer', { releaseRules: [ { type: 'docs',...

tiagoporto

Calling to @semantic-release/commit-analyzer nothing is shown, no error, no success

1

Upon calling @semantic-release/commit-analyzer base on the config in my `.releaserc.js`, in the bitbucket pipeline nothing is showing, there're commit to be analyzed but the plugin just say starting, but there's...

richiesreng