conventionalcommits preset not being picked up?

[timothystone-knsl]

I'm pretty sure this use to work, but I'm not sure when it stopped (possibly with v23, though I haven't had luck downgrading to v22). The file, .releaserc.yml is being read:

[3:07:56 PM] [semantic-release] › ℹ  Running semantic-release version 23.0.8
2024-05-06T15:07:56.520Z semantic-release:config load config from: /builds/another15y/commit-config-presets/.releaserc.yml
2024-05-06T15:07:56.528Z semantic-release:config options values: {
  branches: [ 'master', 'main' ],
  repositoryUrl: '[https://gitlab-ci-token:[secure]@gitlab.com/another15y/commit-config-presets.git'](https://gitlab-ci-token:%5Bsecure%5D@gitlab.com/another15y/commit-config-presets.git'),
  tagFormat: '${version}',
  plugins: [
    [ '@semantic-release/commit-analyzer', [Object] ],
    [ '@semantic-release/release-notes-generator', [Object] ],
    '@semantic-release/gitlab',
    [ '@semantic-release/npm', [Object] ],
    [ '@semantic-release/changelog', [Object] ],
    '@semantic-release/git'
  ],
  _: [],
  debug: true,
  ci: true,
  '$0': 'semantic-release'
}

Setting the preset: 'conventionalcommits' is not behaving as expected. I even tried passing an empty presetConfig: {} because the documentation for the commit-analyzer suggests it's necessary.

Pretty sure I'm getting the syntax correct for the commits, i.e., feat!: something important to bump the major\n\nhands typing words. I have some sample pipelines showing it failing.

[3:08:00 PM] [semantic-release] › ℹ  Start step "analyzeCommits" of plugin "@semantic-release/commit-analyzer"
[3:08:00 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  Analyzing commit: feat(config)!: turn on conventionalcommits and pass a config correctly
The presetConfig was not passed to the configuration correctly. Turn on conventionalcommits and set
the semantic release to latest.
2024-05-06T15:08:00.022Z semantic-release:commit-analyzer Analyzing with default rules
[3:08:00 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  The commit should not trigger a release
[3:08:00 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  Analyzing commit: fix(config)!: pass empty presetConfig
Per semrel documentation, "For presets that expects a configuration object, such as
conventionalcommits, the presetConfig option must be set." Setting one.
2024-05-06T15:08:00.023Z semantic-release:commit-analyzer Analyzing with default rules
[3:08:00 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  The commit should not trigger a release
[3:08:00 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  Analyzing commit: feat!: dowgrade to sem-rel 22x
22.0.12 downgrade.
2024-05-06T15:08:00.023Z semantic-release:commit-analyzer Analyzing with default rules
[3:08:00 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  The commit should not trigger a release
[3:08:00 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  Analyzing commit: feat!: only bang commit in list
updated dummy.txt
2024-05-06T15:08:00.024Z semantic-release:commit-analyzer Analyzing with default rules
[3:08:00 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  The commit should not trigger a release
[3:08:00 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  Analysis of 4 commits complete: no release
[3:08:00 PM] [semantic-release] › ✔  Completed step "analyzeCommits" of plugin "@semantic-release/commit-analyzer"
[3:08:00 PM] [semantic-release] › ℹ  There are no relevant changes, so no new version is released.

Take note that commit-analyzer is "...analyzing with default rules." That seems... incorrect. 🤔

What am I doing wrong in the configuration?

plugins:
  - - '@semantic-release/commit-analyzer'
    - preset: "conventionalcommits"
      presetConfig: {}
  - - '@semantic-release/release-notes-generator'
    - preset: "conventionalcommits"
      presetConfig: {}
  - '@semantic-release/gitlab'
  - - '@semantic-release/npm'
    - npmPublish: false
  - - '@semantic-release/changelog'
    - changelogTitle: |-
        # Another Caffeinated Day Project CHANGELOG

        **Do not edit this file; it is automatically generated by Semantic Release.**
  - '@semantic-release/git'
branches:
  - 'master'
  - 'main'
tagFormat: '${version}'

[timothystone-knsl]

This works locally... npx -- semantic-release --dryRun --debug --ci 🤔

2024-05-06T19:44:42.109Z semantic-release:get-commits Use from: 51f7b5982f0e7a609b0567a34ea2498875302c14
[3:44:42 PM] [semantic-release] › ℹ  Found 4 commits since last release
2024-05-06T19:44:42.139Z semantic-release:get-commits Parsed commits: [ { commit: { long: '55792d171a12a02d49131761a11aa5231576d2e9', short: '55792d17' }, tree: { long: 'ffba038f37727bcfb1adceafb127a704e25ec0db', short: 'ffba038f' }, author: { name: 'Timothy Stone', email: 'tim.stone@kinsaleins.com', date: 2024-05-06T15:02:31.000Z }, committer: { name: 'Timothy Stone', email: 'tim.stone@kinsaleins.com', date: 2024-05-06T15:02:31.000Z }, subject: 'feat(config)!: turn on conventionalcommits and pass a config correctly', body: 'The presetConfig was not passed to the configuration correctly. Turn on conventionalcommits and set\n' + 'the semantic release to latest.\n', hash: '55792d171a12a02d49131761a11aa5231576d2e9', committerDate: 2024-05-06T15:02:31.000Z, message: 'feat(config)!: turn on conventionalcommits and pass a config correctly\n' + '\n' + 'The presetConfig was not passed to the configuration correctly. Turn on conventionalcommits and set\n' + 'the semantic release to latest.', gitTags: '(HEAD -> master, origin/test/correct-presetConfig, test/correct-presetConfig)' }, { commit: { long: '8a644eb7659c5b17c3888d54b484d60d9d0ebd49', short: '8a644eb7' }, tree: { long: '0b4ca408093e34b310750942a139936555b1ddc1', short: '0b4ca408' }, author: { name: 'Timothy Stone', email: 'tim.stone@kinsaleins.com', date: 2024-05-06T14:54:33.000Z }, committer: { name: 'Timothy Stone', email: 'tim.stone@kinsaleins.com', date: 2024-05-06T14:54:33.000Z }, subject: 'fix(config)!: pass empty presetConfig', body: 'Per semrel documentation, "For presets that expects a configuration object, such as\n' + 'conventionalcommits, the presetConfig option must be set." Setting one.\n', hash: '8a644eb7659c5b17c3888d54b484d60d9d0ebd49', committerDate: 2024-05-06T14:54:33.000Z, message: 'fix(config)!: pass empty presetConfig\n' + '\n' + 'Per semrel documentation, "For presets that expects a configuration object, such as\n' + 'conventionalcommits, the presetConfig option must be set." Setting one.', gitTags: '(origin/master, origin/HEAD)' }, { commit: { long: '77093052d8f1a4a6c2be73c10d7fad93c2dcedd9', short: '77093052' }, tree: { long: 'f5886487452914d293680734bab1e18a1244b1f5', short: 'f5886487' }, author: { name: 'Timothy Stone', email: 'gitlab@petmystone.com', date: 2024-05-05T18:20:08.000Z }, committer: { name: 'Timothy Stone', email: 'gitlab@petmystone.com', date: 2024-05-05T18:20:08.000Z }, subject: 'feat!: dowgrade to sem-rel 22x', body: '22.0.12 downgrade.\n', hash: '77093052d8f1a4a6c2be73c10d7fad93c2dcedd9', committerDate: 2024-05-05T18:20:08.000Z, message: 'feat!: dowgrade to sem-rel 22x\n\n22.0.12 downgrade.', gitTags: '' }, { commit: { long: '2f977e69de12b87df78fe5313a56449c2c2fdf20', short: '2f977e69' }, tree: { long: '9af372b7ccbdd64b25967c5893aa6ac3fcb70685', short: '9af372b7' }, author: { name: 'Timothy Stone', email: 'gitlab@petmystone.com', date: 2024-05-05T17:55:50.000Z }, committer: { name: 'Timothy Stone', email: 'gitlab@petmystone.com', date: 2024-05-05T17:58:00.000Z }, subject: 'feat!: only bang commit in list', body: 'updated dummy.txt\n', hash: '2f977e69de12b87df78fe5313a56449c2c2fdf20', committerDate: 2024-05-05T17:58:00.000Z, message: 'feat!: only bang commit in list\n\nupdated dummy.txt', gitTags: '' } ]
[3:44:42 PM] [semantic-release] › ℹ  Start step "analyzeCommits" of plugin "@semantic-release/commit-analyzer"
[3:44:42 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  Analyzing commit: feat(config)!: turn on conventionalcommits and pass a config correctly

The presetConfig was not passed to the configuration correctly. Turn on conventionalcommits and set
the semantic release to latest.
2024-05-06T19:44:42.147Z semantic-release:commit-analyzer Analyzing with default rules
2024-05-06T19:44:42.148Z semantic-release:commit-analyzer The rule { breaking: true, release: 'major' } match commit with release type 'major'
2024-05-06T19:44:42.148Z semantic-release:commit-analyzer Release type 'major' is the highest possible. Stop analysis.
[3:44:42 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  The release type for the commit is major
[3:44:42 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  Analysis of 4 commits complete: major release
[3:44:42 PM] [semantic-release] › ✔  Completed step "analyzeCommits" of plugin "@semantic-release/commit-analyzer"
[3:44:42 PM] [semantic-release] › ℹ  The next release version is 2.0.0
[3:44:42 PM] [semantic-release] › ℹ  Start step "generateNotes" of plugin "@semantic-release/release-notes-generator"

[timothystone-knsl]

This is a sequencing issue in the pipeline templates being used. The required dependencies are being installed, but not available to the job. Sorting out that the dependencies, including semantic-release, are installed globally in the pipeline. How that changes behavior or not is being understood.

Closing this.