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

[renovate]

This PR contains the following updates:

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

---

Release Notes

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

v21.0.5

Compare Source

Bug Fixes

• deps: update dependency marked to v5 (452e1fa)

v21.0.4

Compare Source

Bug Fixes

• deps: update dependency @​semantic-release/error to v4 (d259350)

v21.0.3

Compare Source

Bug Fixes

• bump @semantic-release/commit-analyzer to v10.0.0-beta.1 (4a6b31f)
• bump @semantic-release/github to 9.0.0-beta.2 (#​2818) (6f19d77)
• deps: updated the beta plugins to stable versions (3941018)

v21.0.2

Compare Source

Bug Fixes

• deps: update dependency @​semantic-release/release-notes-generator to v11 (#​2778) (ac40804)

v21.0.1

Compare Source

Bug Fixes

• deps: update dependency env-ci to v9 (#​2757) (4bddb37)

v21.0.0

Compare Source

BREAKING CHANGES

• deps: the npm plugin has updated the npm dependency to v9
• legacy authentication using NPM_USERNAME and NPM_PASSWORD is no longer supported. Use NPM_TOKEN instead.

Bug Fixes

• deps: bump @semantic-release/npm to ^10.0.0 (d647433)

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: 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 has been generated by Mend Renovate. View repository job log here.

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: yarn.lock

Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit