Upgrade conventionalcommits preset to v10

[vspallas-flyr]

Hello,

It seems after fixing the issue conventional-changelog/conventional-changelog/issues/1476, new GitHub Releases do not contain Release Notes anymore.

Our setup is fairly simple:

.releaserc:

{
    "branches": [
      "main",
      {
        "name": "release/+([0-9])?(.{+([0-9]),x}).x",
        "range": "${name.replace(/^release\\//g, '')}"
      },
      "next",
      { "name": "alpha", "prerelease": true },
      { "name": "beta", "prerelease": true },
      { "name": "rc", "prerelease": true }
    ],
    "plugins": [
      [
        "@semantic-release/commit-analyzer",
        {
          "preset": "conventionalcommits"
        }
      ],
      [
        "@semantic-release/release-notes-generator",
        {
          "preset": "conventionalcommits",
          "presetConfig": {
            "preset": {
              "name": "conventionalchangelog"
            }
          }
        }
      ],
      "@semantic-release/github"
    ]
  }

CI:

      - name: Semantic Release
        id: semantic_release
        uses: cycjimmy/semantic-release-action@9246c0bd17405b1f20450501f39234912258bc50 #v6
        with:
          semantic_version: 25.0.5
          dry_run: ${{ inputs.dryRun }}
          extra_plugins: |
            @semantic-release/changelog
            @semantic-release/git
            conventional-changelog-conventionalcommits
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

Setting the conventional-changelog-conventionalcommits to version v9.3.1 resolves the issue.

[travi]

v10 includes breaking changes. since it was released only days ago, we have not even evaluated what needs to be updated here to be compatible with the latest release. between those breaking changes and the fact that supported node versions are now restricted beyond our current support range, updating our support will not be able to happen until we release a new major version, which will not happen automatically.

please do not assume that updating to new major versions of companion dependencies is safe. you are responsible for ensuring compatibility of the plugins you use with semantic-release

[vspallas-flyr]

Hi @travi, thanks for replying!

I know v10 has breaking changes, I just thought to open the issue for transparency.

One question, though, about:

please do not assume that updating to new major versions of companion dependencies is safe. you are responsible for ensuring compatibility of the plugins you use with semantic-release

Isn't conventionalcommits a supported plugin for semantic-release? Since this dependency is used on these repositories, how are we responsible for compatibility? Is there some other plugin that semantic-release supports instead?

[travi]

Isn't conventionalcommits a supported plugin for semantic-release? Since this dependency is used on these repositories, how are we responsible for compatibility?

you might be flirting with the line between compatible and supported with this question. this plugin is not maintained by this project. the timing of its release is not coordinated with our team. our plugin system supports the interface defined by the conventional-changelog presets. when breaking changes are made to that series of presets, the interface changes and our project needs to react to account for those breaking interface changes. because the interface changed, that means that the interface of our plugin system must also change to support the new interface. that means breaking changes for us. we will work through that process, but it is not immediate.

Is there some other plugin that semantic-release supports instead?

the preset you chose to use with your project is installed as a separate dependency. that means that you need to make sure that the version you have installed meets the interface expectations of our plugin system. if you want the compatibility to be guaranteed, we include the package for the angular preset by default, so that preset has better assurances to always be compatible (as long as it is not also installed separately, which can result in conflicts)

[travi]

also keep in mind that the action you are using is also not supported by our team and is not our recommended approach for usage. if you want guidance for usage in the context of that action, please reach out to the team that maintains that action

[vspallas-flyr]

this plugin is not maintained by this project. the timing of its release is not coordinated with our team.

I know. This is why I raised the issue to conventional-changelog (conventional-changelog/conventional-changelog#1494) in the first place, but I got redirected here.

Should I keep the issue open here, or is it not related at all for this repo?

[travi]

It is valid that will l we will need to update our project to be compatible with the updated interface. However, we do not depend directly on this preset, so there is no update for us to perform specifically related to that. Your project is what depends on that package. For now, you need to downgrade to the previous major version.

[travi]

same problem as semantic-release/release-notes-generator#992