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

[renovate[bot]]

This PR contains the following updates:

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

---

Release Notes

semantic-release/semantic-release

### [`v21.0.2`](https://togithub.com/semantic-release/semantic-release/releases/tag/v21.0.2) [Compare Source](https://togithub.com/semantic-release/semantic-release/compare/v21.0.1...v21.0.2) ##### Bug Fixes - **deps:** update dependency [@​semantic-release/release-notes-generator](https://togithub.com/semantic-release/release-notes-generator) to v11 ([#​2778](https://togithub.com/semantic-release/semantic-release/issues/2778)) ([ac40804](https://togithub.com/semantic-release/semantic-release/commit/ac40804dc4b90df783bbee3e439e03cefb76c47f)) ### [`v21.0.1`](https://togithub.com/semantic-release/semantic-release/releases/tag/v21.0.1) [Compare Source](https://togithub.com/semantic-release/semantic-release/compare/v21.0.0...v21.0.1) ##### Bug Fixes - **deps:** update dependency env-ci to v9 ([#​2757](https://togithub.com/semantic-release/semantic-release/issues/2757)) ([4bddb37](https://togithub.com/semantic-release/semantic-release/commit/4bddb37de2fc6743a82299e277d5852d153e2ba8)) ### [`v21.0.0`](https://togithub.com/semantic-release/semantic-release/releases/tag/v21.0.0) [Compare Source](https://togithub.com/semantic-release/semantic-release/compare/v20.1.3...v21.0.0) ##### 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](https://togithub.com/semantic-release/semantic-release/commit/d647433c201a607834a19f6771eb7deaeb709fff))

---

Configuration

📅 Schedule: Branch creation - "before 3am on the first day of the month" (UTC), 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 preset from . View repository job log here

[renovate[bot]]

⚠ 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: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @sanity/semantic-release-preset@4.0.0
npm ERR! Found: semantic-release@21.0.0
npm ERR! node_modules/semantic-release
npm ERR!   dev semantic-release@"^21.0.0" from the root project
npm ERR!   peer semantic-release@">=18.0.0" from @semantic-release/changelog@6.0.2
npm ERR!   node_modules/@semantic-release/changelog
npm ERR!     @semantic-release/changelog@"^6" from @sanity/semantic-release-preset@4.0.0
npm ERR!     node_modules/@sanity/semantic-release-preset
npm ERR!       dev @sanity/semantic-release-preset@"^4.0.0" from the root project
npm ERR!   6 more (@semantic-release/commit-analyzer, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer semantic-release@"^20" from @sanity/semantic-release-preset@4.0.0
npm ERR! node_modules/@sanity/semantic-release-preset
npm ERR!   dev @sanity/semantic-release-preset@"^4.0.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: semantic-release@20.1.3
npm ERR! node_modules/semantic-release
npm ERR!   peer semantic-release@"^20" from @sanity/semantic-release-preset@4.0.0
npm ERR!   node_modules/@sanity/semantic-release-preset
npm ERR!     dev @sanity/semantic-release-preset@"^4.0.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate-cache/others/npm/_logs/2023-04-01T02_09_14_770Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate-cache/others/npm/_logs/2023-04-01T02_09_14_770Z-debug-0.log