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

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@semantic-release/commit-analyzer	11.1.0 -> 13.0.0
@semantic-release/github	9.2.6 -> 10.3.5
@semantic-release/npm	11.0.3 -> 12.0.1
@semantic-release/release-notes-generator	12.1.0 -> 14.0.1
semantic-release	22.0.12 -> 24.1.1

---

Release Notes

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

v13.0.0

Compare Source

Bug Fixes

• log the raw message again (e2f5d6c)

Features

• support latest conventional-changelog packages (0254d7a)

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

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.3.5

Compare Source

Bug Fixes

• replace searchAPI usage with GraphQL in findSRIssue util (#​907) (7fb46a3)

v10.3.4

Compare Source

v10.3.3

Compare Source

Bug Fixes

• Revert: feat: verify OAuth scopes of classic GitHub PATs (#​915) (990bd73)

v10.3.2

Compare Source

Bug Fixes

• missing "PullRequest".canBeRebased field on GHES graphql api (#​913) (4393578)

v10.3.1

Compare Source

Bug Fixes

• max_node_limit_exceeded error when fetching associatedPRs (#​912) (bb806af)

v10.3.0

Compare Source

Features

• allow conditional skip on success and fail comments (#​874) (e097d1c)

v10.2.0

Compare Source

Features

• verify OAuth scopes of classic GitHub PATs (#​897) (be071a2)

v10.1.7

Compare Source

Bug Fixes

• ignore case when checking for repo rename (#​903) (2b1b9b6), closes #​901

v10.1.6

Compare Source

v10.1.5

Compare Source

Bug Fixes

• compare only / when checking for rename (#​886) (24ea2ee)

v10.1.4

Compare Source

Bug Fixes

• docs: correct docs branch for fail-comment links (#​893) (b591730)

v10.1.3

Compare Source

Bug Fixes

• Revert "fix: failing release due to renamed repository (#​878)" (#​887) (325952e)

v10.1.2

Compare Source

Bug Fixes

• failing release due to renamed repository (#​878) (76fdaa3)

v10.1.1

Compare Source

Bug Fixes

• invalid GraphQL query generated when no release commits are found (#​876) (8ee2744)

v10.1.0

Compare Source

Features

• use branch prerelease property for detection (#​863) (45b8da9)

v10.0.7

Compare Source

Bug Fixes

• replace github search api with graphql in success lifecycle method (#​857) (be394cf)

v10.0.6

Compare Source

Bug Fixes

• corrected homepage link in package.json so the generated links in the errors are valid (#​848) (865762d)

v10.0.5

Compare Source

Bug Fixes

• normalize GitHub API URL (#​839) (1e66974)

v10.0.4

Compare Source

Bug Fixes

• introduce dedicated option for GitHub API endpoint (#​829) (908ff83)

v10.0.3

Compare Source

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/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

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

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.1.1

Compare Source

v24.1.0

Compare Source

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.

👻 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 was generated by Mend Renovate. View the repository job log.