ci(deps): update semantic-release monorepo (major)

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@semantic-release/commit-analyzer	^11.0.0 -> ^12.0.0
@semantic-release/github	^9.0.0 -> ^10.0.0
@semantic-release/release-notes-generator	^12.0.0 -> ^13.0.0
semantic-release	^22.0.0 -> ^23.0.0

---

Release Notes

semantic-release/commit-analyzer (@​semantic-release/commit-analyzer)

v12.0.0

Compare Source

Features

• exports: defined exports to point at ./index.js (f3358dd)
• node-versions: dropped support for node v18 and v19 (0a23b82)

BREAKING CHANGES

• exports: exports has been defined, which prevents access to private apis (which arent
  intended for consumption anyway)
• node-versions: node v18 and v19 are no longer supported

semantic-release/github (@​semantic-release/github)

v10.0.2

Compare Source

Bug Fixes

• deps: update octokit monorepo (major) (#​792) (97e368d)

v10.0.1

Compare Source

Bug Fixes

• deps: update dependency issue-parser to v7 (#​798) (8140ba8)

v10.0.0

Compare Source

Features

• node-versions: dropped support for node v18 and v19 (#​797) (aea314f)

BREAKING CHANGES

• node-versions: node v18 and v19 are no longer supported

semantic-release/release-notes-generator (@​semantic-release/release-notes-generator)

v13.0.0

Compare Source

Features

• exports: defined exports to point at ./index.js (5655b18)
• node-versions: dropped support for node v18 and v19 (e65959a)

BREAKING CHANGES

• exports: exports has been defined, which prevents access to private apis (which arent
  intended for consumption anyway)
• node-versions: node v18 and v19 are no longer supported

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

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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• 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: .release/package-lock.json

npm ERR! nested aliases not supported

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-04-20T11_19_28_651Z-debug.log

[kayman-mk]

Auto approved Renovate PR by organization

[kayman-mk]

Auto approved Renovate PR by organization

[kayman-mk]

Auto approved Renovate PR by organization

[kayman-mk]

Auto approved Renovate PR by organization

[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: .release/package-lock.json

npm ERR! nested aliases not supported

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-05-11T14_00_16_440Z-debug.log