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

This MR contains the following updates:

Package	Type	Update	Change
@semantic-release/npm	devDependencies	major	11.0.2 -> 12.0.1
@semantic-release/release-notes-generator	devDependencies	major	^12.1.0 -> ^14.0.0
semantic-release	devDependencies	major	^22.0.12 -> ^24.0.0

---

Release Notes

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

v12.0.1

Compare Source

Bug Fixes

• deps: update dependency execa to v9 (9ac5ed0)

v12.0.0

Compare Source

Features

• exports: defined exports to point at ./index.js (9e193c2)
• node-versions: dropped support for node v18 and v19 (2df962b)

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

v11.0.3

Compare Source

Bug Fixes

• deps: raised the minimum accepted range of npm to v10.5.0 (#​759) (a0313f8), closes semantic-release/semantic-release#3202

even though our existing range allowed anyone to update as soon as the new npm version was available, this will encourage being on a version that does not report the ip vulnerability a bit more forcefully

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

v14.0.2

Compare Source

Bug Fixes

• AWS CodeCommit compatibility (#​748) (687e2e2)

v14.0.1

Compare Source

Bug Fixes

• deps: rename read-pkg-up to read-package-up (#​671) (687ba5a)

v14.0.0

Compare Source

Features

• support latest conventional-changelog packages (#​643) (2bce0d3)

BREAKING CHANGES

• by supporting the latest major versions of conventional-changelog packages, we are dropping support for previous major versions of those packages due to the breaking changes between majors. this only impacts your project if you are installing alongside semantic-release, so updating those packages to latest version should be the only change you need for this update. no action should be necessary if you are using default semantic-release config

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)

v24.2.0

Compare Source

Features

• clarify branch existence requirement in error messages (#​3462) (05a2ea9)

v24.1.3

Compare Source

Bug Fixes

• branch-naming: prevent non-range versions from being identified as maintenance branches (07f2672)

v24.1.2

Compare Source

Bug Fixes

• deps: update @semantic-release/github to v11.0.0 (#​3460) (43df51b)

v24.1.1

Compare Source

Bug Fixes

• deps: update dependency hosted-git-info to v8 (#​3436) (ab10ac1)

v24.1.0

Compare Source

Features

• add warn type to global context.logger (#​3423) (bcc663c)

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

Bug Fixes

• deps: update dependency execa to v9 (#​3296) (73bcd0b)

v23.1.0

Compare Source

Features

• add main branch to default release branch config (#​1737) (95d8736)

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

Bug Fixes

• deps: update dependency find-versions to v6 (6a2b6bb)

v23.0.6

Compare Source

Bug Fixes

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

v23.0.5

Compare Source

Bug Fixes

• deps: update dependency @​semantic-release/commit-analyzer to v12 (#​3226) (29458a0)

v23.0.4

Compare Source

Bug Fixes

• deps: update dependency @​semantic-release/npm to v12 (#​3224) (7a50c8a)

v23.0.3

Compare Source

Bug Fixes

• deps: update dependency @​semantic-release/github to v10 (#​3222) (96d5aeb)

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 or renamed to .releaserc.js to keep it in the root of the repository. 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 MR is behind base branch, or you tick the rebase/retry checkbox.

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

---

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

---

This MR has been generated by Renovate Bot.