"BREAKING CHANGE" not triggering release

[iot-resister]

I'm trying to understand the api in a sandbox. I'm merely trying to trigger a release ina dummy repo. No luck though.

Gitlab CI Output:

[1:55:33 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  Analyzing commit: BREAKING CHANGE: Test
[1:55:33 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  The commit should not trigger a release

Not using a git flow. Pushing straight to master. Here is my .releaserc.json

{
  "branches": ["master"],
  "plugins": [
    "@semantic-release/commit-analyzer",
    "@semantic-release/release-notes-generator",
    ["@semantic-release/gitlab", {
      "gitlabUrl": "https://gitlab.com",
      "assets": [
        {"path": "index.js", "label": "JS distribution"}
      ]
    }]
  ]
}

[gr2m]

Can you run semantic-release --debug and share the full logs?

[iot-resister]

Sure. Thanks for the quick response. This is my full output.

$ yarn semantic-release
yarn run v1.22.5
$ semantic-release --debug
[2:21:43 PM] [semantic-release] › ℹ  Running semantic-release version 17.3.8
2021-02-12T20:21:43.671Z semantic-release:config load config from: /home/dio/builds/[secure]/0/Resister/semantic-gitlab/.releaserc.json
2021-02-12T20:21:43.705Z semantic-release:config options values: {
  branches: [ 'master' ],
  repositoryUrl: 'https://gitlab.com/Resister/semantic-gitlab.git',
  tagFormat: 'v${version}',
  plugins: [
    '@semantic-release/commit-analyzer',
    '@semantic-release/release-notes-generator',
    [ '@semantic-release/gitlab', [Object] ]
  ],
  _: [],
  debug: true,
  '$0': 'node_modules/.bin/semantic-release'
}
2021-02-12T20:21:45.043Z semantic-release:plugins options for @semantic-release/gitlab/verifyConditions: {
  gitlabUrl: 'https://gitlab.com',
  assets: [ { path: 'index.js', label: 'JS distribution' } ]
}
[2:21:45 PM] [semantic-release] › ✔  Loaded plugin "verifyConditions" from "@semantic-release/gitlab"
2021-02-12T20:21:45.051Z semantic-release:plugins options for @semantic-release/commit-analyzer/analyzeCommits: {}
[2:21:45 PM] [semantic-release] › ✔  Loaded plugin "analyzeCommits" from "@semantic-release/commit-analyzer"
2021-02-12T20:21:45.054Z semantic-release:plugins options for @semantic-release/release-notes-generator/generateNotes: {}
[2:21:45 PM] [semantic-release] › ✔  Loaded plugin "generateNotes" from "@semantic-release/release-notes-generator"
2021-02-12T20:21:45.058Z semantic-release:plugins options for @semantic-release/gitlab/publish: {
  gitlabUrl: 'https://gitlab.com',
  assets: [ { path: 'index.js', label: 'JS distribution' } ]
}
[2:21:45 PM] [semantic-release] › ✔  Loaded plugin "publish" from "@semantic-release/gitlab"
2021-02-12T20:21:45.228Z semantic-release:get-git-auth-url Verifying ssh auth by attempting to push to  https://gitlab.com/Resister/semantic-gitlab.git
2021-02-12T20:21:46.048Z semantic-release:git Error: Command failed with exit code 128: git push --dry-run --no-verify https://gitlab.com/Resister/semantic-gitlab.git HEAD:master
remote: HTTP Basic: Access denied
fatal: Authentication failed for 'https://gitlab.com/Resister/semantic-gitlab.git/'
    at makeError (/home/dio/builds/[secure]/0/Resister/semantic-gitlab/node_modules/semantic-release/node_modules/execa/lib/error.js:59:11)
    at handlePromise (/home/dio/builds/[secure]/0/Resister/semantic-gitlab/node_modules/semantic-release/node_modules/execa/index.js:114:26)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    at async verifyAuth (/home/dio/builds/[secure]/0/Resister/semantic-gitlab/node_modules/semantic-release/lib/git.js:207:5)
    at async module.exports (/home/dio/builds/[secure]/0/Resister/semantic-gitlab/node_modules/semantic-release/lib/get-git-auth-url.js:91:5)
    at async run (/home/dio/builds/[secure]/0/Resister/semantic-gitlab/node_modules/semantic-release/index.js:56:27)
    at async module.exports (/home/dio/builds/[secure]/0/Resister/semantic-gitlab/node_modules/semantic-release/index.js:260:22)
    at async module.exports (/home/dio/builds/[secure]/0/Resister/semantic-gitlab/node_modules/semantic-release/cli.js:55:5)
2021-02-12T20:21:46.049Z semantic-release:get-git-auth-url SSH key auth failed, falling back to https.
2021-02-12T20:21:49.059Z semantic-release:get-tags found tags for branch master: [ { gitTag: 'v1.0.0', version: '1.0.0', channels: [ null ] } ]
[2:21:49 PM] [semantic-release] › ✔  Run automated release from branch master on repository https://gitlab-ci-token:[secure]@gitlab.com/Resister/semantic-gitlab.git
[2:21:49 PM] [semantic-release] › ✔  Allowed to push to the Git repository
[2:21:49 PM] [semantic-release] › ℹ  Start step "verifyConditions" of plugin "@semantic-release/gitlab"
2021-02-12T20:21:49.974Z semantic-release:gitlab apiUrl: 'https://gitlab.com/api/v4'
2021-02-12T20:21:49.975Z semantic-release:gitlab repoId: 'Resister/semantic-gitlab'
[2:21:49 PM] [semantic-release] [@semantic-release/gitlab] › ℹ  Verify GitLab authentication (https://gitlab.com/api/v4)
[2:21:50 PM] [semantic-release] › ✔  Completed step "verifyConditions" of plugin "@semantic-release/gitlab"
[2:21:50 PM] [semantic-release] › ℹ  Found git tag v1.0.0 associated with version 1.0.0 on branch master
2021-02-12T20:21:50.607Z semantic-release:get-commits Use from: a88c4967967eac138b4ce18e8b32883c636934a6
[2:21:50 PM] [semantic-release] › ℹ  Found 3 commits since last release
2021-02-12T20:21:50.692Z semantic-release:get-commits Parsed commits: [ { commit: { long: 'da205fe376716c7bbb4382c5a972cc6bf9d137ed', short: 'da205fe' }, tree: { long: '7a260926185d550f5b609ed625886018cc9dfb9c', short: '7a26092' }, author: { name: 'Resister', email: 'iot.resister@protonmail.com', date: 2021-02-12T20:22:56.000Z }, committer: { name: 'Resister', email: 'iot.resister@protonmail.com', date: 2021-02-12T20:22:56.000Z }, subject: 'BREAKING CHANGES', body: '', hash: 'da205fe376716c7bbb4382c5a972cc6bf9d137ed', committerDate: 2021-02-12T20:22:56.000Z, message: 'BREAKING CHANGES', gitTags: '(HEAD, origin/master, refs/pipelines/255628186, master)' }, { commit: { long: '074668a44a4ee9145fb5cd325e440e45c04a05b3', short: '074668a' }, tree: { long: '59e676937db9ba3ca50ebf055eb3acf96cdff4d3', short: '59e6769' }, author: { name: 'Resister', email: 'iot.resister@protonmail.com', date: 2021-02-12T20:06:45.000Z }, committer: { name: 'Resister', email: 'iot.resister@protonmail.com', date: 2021-02-12T20:06:45.000Z }, subject: 'BREAKING CHANGES', body: '', hash: '074668a44a4ee9145fb5cd325e440e45c04a05b3', committerDate: 2021-02-12T20:06:45.000Z, message: 'BREAKING CHANGES', gitTags: '(refs/pipelines/255619703)' }, { commit: { long: '1bc32417e9ff6ac153a75412cf09eddc4faddc30', short: '1bc3241' }, tree: { long: 'ef44a094de22bf25bf02d25cd0484711ce625f53', short: 'ef44a09' }, author: { name: 'Resister', email: 'iot.resister@protonmail.com', date: 2021-02-12T19:56:38.000Z }, committer: { name: 'Resister', email: 'iot.resister@protonmail.com', date: 2021-02-12T19:56:38.000Z }, subject: 'BREAKING CHANGE: Rap', body: '', hash: '1bc32417e9ff6ac153a75412cf09eddc4faddc30', committerDate: 2021-02-12T19:56:38.000Z, message: 'BREAKING CHANGE: Rap', gitTags: '(refs/pipelines/255615587)' } ]
[2:21:50 PM] [semantic-release] › ℹ  Start step "analyzeCommits" of plugin "@semantic-release/commit-analyzer"
[2:21:50 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  Analyzing commit: BREAKING CHANGES
2021-02-12T20:21:50.766Z semantic-release:commit-analyzer Analyzing with default rules
[2:21:50 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  The commit should not trigger a release
[2:21:50 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  Analyzing commit: BREAKING CHANGES
2021-02-12T20:21:50.770Z semantic-release:commit-analyzer Analyzing with default rules
[2:21:50 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  The commit should not trigger a release
[2:21:50 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  Analyzing commit: BREAKING CHANGE: Rap
2021-02-12T20:21:50.772Z semantic-release:commit-analyzer Analyzing with default rules
[2:21:50 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  The commit should not trigger a release
[2:21:50 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  Analysis of 3 commits complete: no release
[2:21:50 PM] [semantic-release] › ✔  Completed step "analyzeCommits" of plugin "@semantic-release/commit-analyzer"
[2:21:50 PM] [semantic-release] › ℹ  There are no relevant changes, so no new version is released.
Done in 10.47s.
Saving cache for successful job 00:41
Creating cache master...
Runtime platform                                    arch=amd64 os=linux pid=13336 revision=775dd39d version=13.8.0
.yarn/: found 17827 matching files and directories 
No URL provided, cache will be not uploaded to shared cache server. Cache will be stored only locally. 
Created cache
Cleaning up file based variables 00:00
Job succeeded

[travi]

Analyzing commit: BREAKING CHANGE: Test

based on this log output, it looks like you are including the BREAKING CHANGE: in the subject of the commit. the default convention used by semantic-release expects this to be in the commit body, unlike feat, fix, etc because any commit type can include a breaking change

[iot-resister]

Thats it! Thanks @travi!