build(deps): update dependency semantic-release to v24

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
semantic-release	22.0.12 -> 24.0.0

---

Release Notes

semantic-release/semantic-release (semantic-release)

v24.0.0

Compare Source

Bug Fixes

• deps: upgraded to the beta of the commit-analyzer plugin (dfc3d91)
• deps: upgraded to the beta of the release-notes-generator plugin (4a4cd92)

BREAKING CHANGES

• deps: the commit-analyzer plugin now expects to be used with the latest major versions of
  conventional-changelog packages. if you are installing any of these packages in addition to
  semantic-release, be sure to update them as well
• deps: the release-notes-generator plugin now expects to be used with the latest major
  versions of conventional-changelog packages. if you are installing any of these packages in addition
  to semantic-release, be sure to update them as well

v23.1.1

Compare Source

v23.1.0

Compare Source

v23.0.8

Compare Source

Bug Fixes

• deps: rename read-pkg-up -> read-package-up (4980cba)
• deps: rename read-pkg-up -> read-package-up (#​3249) (95a8b9e)

v23.0.7

Compare Source

v23.0.6

Compare Source

Bug Fixes

• deps: update dependency @​semantic-release/release-notes-generator to v13 (#​3237) (b7e08fc)

v23.0.5

Compare Source

v23.0.4

Compare Source

v23.0.3

Compare Source

v23.0.2

Compare Source

Bug Fixes

• deps: update dependency marked to v12 (#​3176) (38105f5)

v23.0.1

Compare Source

Bug Fixes

• deps: update dependency marked-terminal to v7 (9faded8)

v23.0.0

Compare Source

Bug Fixes

• deps: update dependency cosmiconfig to v9 (#​3105) (07dde04)
• deps: update dependency marked to v11 (#​3079) (6d2a6f1)
• deps: upgraded to the latest version of env-ci (0d0ed9d)
• use one note reference per tag to prevent conflicts (#​2085) (020ea7d)

Features

• node-versions: dropped support for node v18 and raised the minimum for v20 (2904832), closes /github.com/semantic-release/gitlab/pull/647#discussion_r1423131205

BREAKING CHANGES

• deps: woodpecker ci users need to upgrade to v1.0.0 or higher to remain supported. see
  https://github.com/semantic-release/env-ci/releases/tag/v11.0.0 for more information
• node-versions: support for node v18 has been dropped and the minimum for v20 is now v20.8.1

related to https://github.com/semantic-release/semantic-release/discussions/3088

• deps: if using release.config.js as the name of your config file, it needs to be moved to a .config/ directory. see https://github.com/cosmiconfig/cosmiconfig/releases/tag/v9.0.0 for more detail

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml

.                                        |  WARN  `node_modules` is present. Lockfile only installation will make it out-of-date
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 108, reused 0, downloaded 0, added 0
Progress: resolved 226, reused 0, downloaded 0, added 0
Progress: resolved 272, reused 0, downloaded 0, added 0
Progress: resolved 356, reused 0, downloaded 0, added 0
Progress: resolved 428, reused 0, downloaded 0, added 0
Progress: resolved 492, reused 0, downloaded 0, added 0
Progress: resolved 636, reused 0, downloaded 0, added 0
Progress: resolved 701, reused 0, downloaded 0, added 0
Progress: resolved 779, reused 0, downloaded 0, added 0
Progress: resolved 836, reused 0, downloaded 0, added 0
Progress: resolved 892, reused 0, downloaded 0, added 0
Progress: resolved 1047, reused 0, downloaded 0, added 0
Progress: resolved 1126, reused 0, downloaded 0, added 0
Progress: resolved 1262, reused 0, downloaded 0, added 0
Progress: resolved 1371, reused 0, downloaded 0, added 0
 WARN  7 deprecated subdependencies found: @humanwhocodes/[email protected], @humanwhocodes/[email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
Progress: resolved 1386, reused 0, downloaded 0, added 0
Progress: resolved 1386, reused 0, downloaded 0, added 0, done
 ERR_PNPM_PEER_DEP_ISSUES  Unmet peer dependencies

.
└─┬ semantic-release 24.0.0
  └─┬ @semantic-release/github 10.0.7
    └─┬ @octokit/plugin-paginate-rest 11.3.1
      └── ✕ unmet peer @octokit/core@5: found 6.1.2 in @semantic-release/github

hint: If you don't want pnpm to fail on peer dependency issues, add "strict-peer-dependencies=false" to an .npmrc file at the root of your project.

[rarkins]

@travi any chance you could take a look when you have time? For now I'm rolling back conventional-changelog-conventionalcommits

[travi]

this is an interesting one. it looks like you are pulling in @octokit/plugin-paginate-rest v11.3.1 even though that version is not released to the latest channel (instead released to the cjs channel):

$ npm dist-tags ls @octokit/plugin-paginate-rest
beta: 10.0.0-beta.4
cjs: 11.3.1
latest: 11.3.0
release-1.x: 1.1.2
release-2.x: 2.21.3
release-9.x: 9.2.1

v11.3.1 appears to switch the peer dependency from >=6 to 5 for some reason (maybe cjs support?). using npm, i have not seen this problem with npm. i'm not a pnpm user, but is there a difference there that would result in pulling that version from the other channel?

this seems to be not directly related to semantic-release, so it could be worth opening an issue on the octokit side to see if the team there has more insight.

also worth noting when you do update semantic-release to the latest version, be sure to also update conventional-changelog-conventionalcommits to the latest major as well. breaking changes there are the reason for the most recent major release of semantic-release

[viceice]

we need to use node v20 for release first, otherwise it'll fail to release again

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 24.x releases. But if you manually upgrade to 24.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

[viceice]

@rarkins why do you closed this? I've already merged conventional commits major, so we need this now