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

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@semantic-release/exec	6.0.3 → 7.1.0
@semantic-release/npm	10.0.6 → 13.1.5
semantic-release	21.1.2 → 25.0.3

---

Release Notes

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

v7.1.0

Compare Source

Features

• error: print more useful error for non-process failure (#​449) (a285bc5)

v7.0.3

Compare Source

Bug Fixes

• deps: update dependency execa to v9 (643e2eb)

v7.0.2

Compare Source

Bug Fixes

• deps: update dependency @​semantic-release/error to v4 (#​353) (471f963)

v7.0.1

Compare Source

Bug Fixes

• deps: update dependency parse-json to v8 (#​394) (080440f)

v7.0.0

Compare Source

Features

• ES Module (#​411) (b4462db)

BREAKING CHANGES

• the minimum required version of semantic-release to use @semantic-release/exec is now v24.1.0; the warn logger method/function is now available to use in plugin

• @semantic-release/exec is now a native ES Module. It has named exports for each plugin hook (verifyConditions, analyzeCommits, verifyRelease, generateNotes, prepare, publish, addChannel, success, fail)

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

v13.1.5

Compare Source

Bug Fixes

• deps: update dependency normalize-url to v9 (#​1095) (daec492)

v13.1.4

Compare Source

Bug Fixes

• deps: update dependency @​actions/core to v3 (#​1085) (17abfe1)

v13.1.3

Compare Source

Bug Fixes

• deps: update dependency @​actions/core to v2 (#​1055) (fa4a3ab)

v13.1.2

Compare Source

Bug Fixes

• deps: update dependency read-pkg to v10 (#​1032) (f3f1a00)

v13.1.1

Compare Source

Bug Fixes

• publish-dry-run: temporarily remove the addition of dry-running the publish step (30bd176)

v13.1.0

Compare Source

Features

• trusted-publishing: verify auth, considering OIDC vs tokens from various registries (e3319f1), closes #​958
• trusted-publishing: refine the messages for related errors (316ce21), closes #​958
• trusted-publishing: make request to verify if OIDC token exchange can succeed (c80ecb0), closes #​958
• trusted-publishing: pass id-token as bearer header for github actions (d83b727), closes #​958
• trusted-publishing: pass id-token as bearer header for gitlab pipelines (6d1c3cf), closes #​958
• trusted-publishing: handle failure to retrieve id-token in the context of github actions (b673257), closes #​958
• auth-error: update messaging for auth failure to be less token specific (e24967d)
• auth: attempt a dry-run publish to determine auth status (841dc67)

Bug Fixes

• trusted-publishing: uri encode the package name for the token exchange request (3dd95d0), closes #​958
• auth: throw appropriate error when auth context fails to enable publishing (f5c8d85)
• auth: throw error if dry-run publish determines lack of auth (8f88e9d)
• verify-auth: enable the publish dry-run to work for projects publishing from a sub-directory (e7d684c)

v13.0.0

Compare Source

Features

• node-versions: drop support for node versions v20, v21, and v23
• node-versions: raise the minimum node version requirement for the v24 range (935439e)

Bug Fixes

• deps: update npm to v11 (debc7c5), closes #​966 #​966
• deps: update to the latest version of npm (1b25d6c)

BREAKING CHANGES

• node-versions: the minimum node version for the v24 range is now v24.10.0
• deps: a minimum of node v22.14 is now required

v12.0.2

Compare Source

Bug Fixes

• deps: update npm to ^10.9.3 (#​972) (93e0937)

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

v11.0.2

Compare Source

Bug Fixes

• deps: update dependency npm to v10.2.5 (42b5dec)

v11.0.1

Compare Source

Bug Fixes

• deps: update dependency read-pkg to v9 (#​703) (6e84013)

v11.0.0

Compare Source

Bug Fixes

• deps: update dependency npm to v10 (819f257)

Features

• node-versions: raised the minimum required node version to v18.17 and dropped v19 support (6413130)

BREAKING CHANGES

• node-versions: node v18.17 is now the minimum required version and support for v19 has been dropped

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

v25.0.3

Compare Source

Bug Fixes

• deps: remove deprecated semver-diff (#​3980) (f404124)

v25.0.2

Compare Source

Bug Fixes

• deps: update dependency read-package-up to v12 (#​3935) (1494cb9)

v25.0.1

Compare Source

Bug Fixes

• deps: update to the latest version of the npm plugin to add trusted publishing support (fad173e), closes semantic-release/npm#958

v25.0.0

Compare Source

Bug Fixes

• deps: update dependency hosted-git-info to v9 (9fa04f8)
• deps: update dependency yargs to v18 (#​3745) (cde9a72)
• deps: update to the stable version of the github plugin (f12cf81)
• deps: update to the stable version of the release-notes-generator plugin (d9def72)
• deps: updated to the stable version of the commit-analyzer plugin (291533b)
• deps: upgrade to the new major version of the npm plugin, which upgrades npm to v11 for publishing (1be8290)

Features

• node-versions: drop support for node versions v20, v21, and v23 (56d16f4)
• node-versions: raise the minimum node version for the v24 range (116a188)

BREAKING CHANGES

• node-versions: the minimum node version for the v24 range is now v24.10.0
• node-versions: a minimum of node v22.14 is now required

v24.2.9

Compare Source

Bug Fixes

• deps: update dependency semver-diff to v5 (#​3867) (a834948)

v24.2.8

Compare Source

Bug Fixes

• deps: update dependency hook-std to v4 (#​3859) (67abe56)

v24.2.7

Compare Source

Performance Improvements

• get-tags.js: bulk get for tags notes (#​3732) (85187e2)

v24.2.6

Compare Source

Bug Fixes

• deps: update @​semantic-release/npm to ^12.0.2 (#​3791) (93177d0)

v24.2.5

Compare Source

Bug Fixes

• deps: raise the minimum of the defined range for marked-terminal (#​3742) (fb1ccd4)

v24.2.4

Compare Source

Bug Fixes

• deps: update dependency marked to v15 (#​3499) (e45040e)

v24.2.3

Compare Source

Bug Fixes

• types: fixed typescript definition (0e08b5c), closes #​3601

v24.2.2

Compare Source

Bug Fixes

• get-git-auth-url.js: Added debug for success (#​3595) (2616d93)

v24.2.1

Compare Source

Bug Fixes

• deps: update dependency import-from-esm to v2 (#​3556) (f15019c)

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://redirect.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

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 #​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.

---

Configuration

📅 Schedule: (UTC)

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

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

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm execa is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/semantic-release@25.0.3 → npm/@semantic-release/npm@13.1.5 → npm/@semantic-release/exec@7.1.0 → npm/execa@9.6.1 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/execa@9.6.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm highlight.js is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/semantic-release@25.0.3 → npm/highlight.js@10.7.3 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/highlight.js@10.7.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm npm is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/@semantic-release/npm@13.1.5 → npm/npm@11.14.1 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/npm@11.14.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm npm is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/@semantic-release/npm@13.1.5 → npm/npm@11.14.1 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/npm@11.14.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm npm is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/@semantic-release/npm@13.1.5 → npm/npm@11.14.1 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/npm@11.14.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm npm is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/@semantic-release/npm@13.1.5 → npm/npm@11.14.1 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/npm@11.14.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm npm is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/@semantic-release/npm@13.1.5 → npm/npm@11.14.1 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/npm@11.14.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report