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

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@semantic-release/changelog	5.0.1 -> 6.0.3
@semantic-release/git	9.0.1 -> 10.0.1

---

Release Notes

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

v6.0.3

Compare Source

Bug Fixes

• deps: update dependency fs-extra to v11.1.1 (#​309) (47045b3)

v6.0.2

Compare Source

Bug Fixes

• deps: update dependency fs-extra to v11 (#​276) (404c768)

v6.0.1

Compare Source

Bug Fixes

• deps: update dependency @​semantic-release/error to v3 (#​167) (ef37296)

v6.0.0

Compare Source

Features

• node-version: raised the minimum required version to v14.17 (#​170) (5cf74e4)

BREAKING CHANGES

• node-version: the minimum required version of node is now v14.17

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

v10.0.1

Compare Source

Bug Fixes

• deps: update dependency @​semantic-release/error to v3 (#​295) (3e934d4)

v10.0.0

Compare Source

Features

• node-version: raised the minimum required version to v14.17 (7ab65f8)

BREAKING CHANGES

• node-version: the minimum required version of node is now v14.17

---

Configuration

📅 Schedule: Branch creation - "after 6pm every weekday,every weekend,before 8am every weekday" (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.

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

[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

/usr/local/bin/docker: line 4: .: filename argument required
.: usage: . filename [arguments]
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/semantic-release
npm ERR!   dev semantic-release@"17.4.7" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer semantic-release@">=18.0.0" from @semantic-release/[email protected]
npm ERR! node_modules/@semantic-release/changelog
npm ERR!   dev @semantic-release/changelog@"6.0.3" 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/acfc91/9fc436/cache/others/npm/_logs/2023-08-04T21_07_45_801Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/acfc91/9fc436/cache/others/npm/_logs/2023-08-04T21_07_45_801Z-debug-0.log