chore(deps): update semantic-release to v20

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
semantic-release	^19.0.2 → ^20.1.3

---

Release Notes

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

v20.1.3

Compare Source

Bug Fixes

• deps: update dependency execa to v7.1.1 (c38b53a)

v20.1.2

Compare Source

Bug Fixes

• deps: update dependency cosmiconfig to v8.1.2 (fbede54)

v20.1.1

Compare Source

Bug Fixes

• deps: update dependency execa to v7 (#​2709) (31d9bfe)

v20.1.0

Compare Source

Features

• plugins: add support for loading ESM plugins (#​2688) (d170f73)

v20.0.4

Compare Source

Bug Fixes

• windows: fixed issues preventing execution from windows (#​2672) (5df624c)

v20.0.3

Compare Source

Reverts

• Revert "chore(deps): update dependency ava to v5.1.1" (#​2682) (914b0a2), closes #​2682

v20.0.2

Compare Source

Bug Fixes

• deps: update dependency semver-diff to v4 (#​1915) (cb45d27)

v20.0.1

Compare Source

Bug Fixes

• deps: update dependency cosmiconfig to v8 (f914c1e)
• deps: update dependency hosted-git-info to v6 (c4da008)

v20.0.0

Compare Source

BREAKING CHANGES

• esm: semantic-release is now ESM-only. since it is used through its own executable, the impact on consuming projects should be minimal
• esm: references to plugin files in configs need to include the file extension because of executing in an ESM context
• node-versions: node v18 is now the minimum required version of node. this is in line with our node support policy. please see our recommendations for releasing with a different node version than your project normally uses, if necessary.

Features

• esm: convert to esm (#​2569) (9eab1ad), closes #​2543
• node-versions: raised the minimum required node version to v18 (#​2620) (8a0d8be)

Bug Fixes

• env-ci: updated to the stable esm-only version (#​2632) (918eb59)
• secrets-masking: used the proper named import from hook-std to enable masking for stderr (#​2619) (cf6befa)

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • "before 3am on the first day of the month"
• 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 has been generated by Mend Renovate using a curated preset maintained by . View repository job log here

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	semantic-release@​19.0.5 ⏵ 20.1.3	+1

View full report

[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 js-yaml is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package-lock.json → npm/semantic-release@20.1.3 → npm/js-yaml@4.2.0 ℹ 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/js-yaml@4.2.0. 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