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

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
semantic-release	21.0.5 -> 21.1.2

---

Release Notes

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

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)

v21.0.7

Compare Source

Bug Fixes

• deps: update dependency read-pkg-up to v10 (#​2862) (70996e0)

v21.0.6

Compare Source

Bug Fixes

• get correct version if prerelease branch shares version with ... (#​2416) (e4229f9)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: jest-react@0.14.0
npm ERR! Found: jest@29.6.2
npm ERR! node_modules/jest
npm ERR!   dev jest@"29.6.2" from the root project
npm ERR!   peer jest@"^29.0.0" from ts-jest@29.1.0
npm ERR!   node_modules/ts-jest
npm ERR!     dev ts-jest@"29.1.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer jest@"^23.0.1 || ^24.0.0 || ^25.1.0" from jest-react@0.14.0
npm ERR! node_modules/jest-react
npm ERR!   dev jest-react@"0.14.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: jest@25.5.4
npm ERR! node_modules/jest
npm ERR!   peer jest@"^23.0.1 || ^24.0.0 || ^25.1.0" from jest-react@0.14.0
npm ERR!   node_modules/jest-react
npm ERR!     dev jest-react@"0.14.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/worker/0ea9c1/bfa8d5/cache/others/npm/_logs/2023-09-16T04_49_29_607Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/0ea9c1/bfa8d5/cache/others/npm/_logs/2023-09-16T04_49_29_607Z-debug-0.log