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

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
semantic-release	^21.0.0 -> ^24.0.0

---

Release Notes

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

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

v22.0.12

Compare Source

Bug Fixes

• Revert "fix(deps): update dependency cosmiconfig to v9" (#​3104) (f6f1bf1)

v22.0.11

Compare Source

Bug Fixes

• deps: update dependency cosmiconfig to v9 (b38cd2e)

v22.0.10

Compare Source

Bug Fixes

• revert updating cosmiconfig to v9 (88efead)

v22.0.9

Compare Source

Bug Fixes

• deps: update dependency cosmiconfig to v9 (#​3072) (8b0dbd2)

v22.0.8

Compare Source

Bug Fixes

• support windows absolute extends (#​3062) (0d06f62)

v22.0.7

Compare Source

Bug Fixes

• deps: update dependency read-pkg-up to v11 (#​3047) (f09e55f)

Features

• support extending ESM configuration files (#​3036)(6900865)

v22.0.6

Compare Source

Bug Fixes

• deps: update dependency figures to v6 (#​3033) (305674d)

v22.0.5

Compare Source

Bug Fixes

• deps: update dependency env-ci to v10 (#​2983) (e759493)

v22.0.4

Compare Source

Bug Fixes

• deps: update dependency marked to v9 (#​2947) (84f2ee9)

v22.0.3

Compare Source

Bug Fixes

• exports: removed the exports definition for the time being (561e2d6), closes #​2968. see https://github.com/semantic-release/semantic-release/issues/2978 for more information.

v22.0.2

Compare Source

Bug Fixes

• deps: update dependency marked-terminal to v6 (8a7befe)

v22.0.1

Compare Source

Bug Fixes

• deps: upgraded release-notes-generator and commit-analyzer plugins to stable versions (041e4f7), closes #​2934

v22.0.0

Compare Source

Bug Fixes

• deps: updated to the latest beta of the commit analyzer plugin (03a687b)
• deps: updated to the latest betas of the commit-analyzer and release-notes-generator plugins (de8e4e0)
• deps: upgraded to the latest version of the npm plugin with npm v10 (a23b718)

Features

• conventional-changelog-presets: supported new preset format (07a79ea)
• defined exports for the package (72ab317)
• node-versions: raised the minimum node v20 requirement to v20.6 (e623cc6)
• node-versions: raised the minimum required node version to v18.17 and dropped v19 support (b9f294d)
• node-versions: raised the minimum supported node version w/in the v20 range to v20.6.1 (b93bef4)

BREAKING CHANGES

• node-versions: the minimum supported version for the v20 range of node has been raised slightly to
  v20.6.1 to avoid a known node bug
• node-versions: the minimum supported node version in the v20 major range is now v20.6
• node-versions: node v18.17 is now the minimum supported node version and support for v19 has been dropped
• exports prevents access to internal files, but they arent intended for public use anyway
• conventional-changelog-presets: the new preset format is a breaking change when compared to the previous preset format. updating to support the new format means that the old preset format is no longer supported. update your preset to the latest version to maintain compatibility. this is also important if you are using a preset outside of the list of official conventional-changelog presets since your preset will need to be updated to export async functions to match the expected preset signature.

v21.1.2

Compare Source

Bug Fixes

• deps: update dependency aggregate-error to v5 (#​2956) (1017e1a)

v21.1.1

Compare Source

Bug Fixes

• types: included the definitions file in the published package (#​2920) (4c95c97)

v21.1.0

Compare Source

Features

• Added TypeScript definitions (#​2916) (c21a1ac)

v21.0.9

Compare Source

Bug Fixes

• deps: update dependency hosted-git-info to v7 (#​2908) (eba86ac)

v21.0.8

Compare Source

Bug Fixes

• deps: update dependency execa to v8 (#​2914) (7bc21fc)

---

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

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.