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

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@semantic-release/changelog	3.0.6 → 7.0.0
@semantic-release/git	7.0.18 → 11.0.1

---

Release Notes

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

v7.0.0

Compare Source

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

v5.0.1

Compare Source

Bug Fixes

• package: update fs-extra to version 9.0.0 (997fe15)

v5.0.0

Compare Source

chore

• require Node.js >=10.18 (5ffdf49)

BREAKING CHANGES

• Require Node.js >= 10.18

v4.0.0

Compare Source

Features

• require Node.js >=10.13 (1f483af)

BREAKING CHANGES

• Require Node.js >= 10.13

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

v11.0.1

Compare Source

Bug Fixes

• deps: update dependency execa to v10 (#​564) (b39d5c6)

v11.0.0

Compare Source

Features

• ES Module (#​544) (4d704a2), closes #​491 #​490

BREAKING CHANGES

• @semantic-release/git is now a native ES Module. It
  has named exports for each plugin hook (verifyConditions, prepare)
• the minimum required version of semantic-release to use
  @semantic-release/git is now v20.1.0

Other Notable Changes

• @semantic-release/error ^3 → ^4 (ESM-only)
• aggregate-error ^3 → ^5 (ESM-only, uses native AggregateError)
• execa ^5 → ^9 (ESM-only, named export)
• p-reduce ^2 → ^3 (ESM-only)
• Removed CJS-only devDeps: clear-module, file-url, fs-extra,
  get-stream, nyc
• Added c8 for coverage; bumped ava, sinon, tempy,
  semantic-release, prettier
• Engine: ^22.22.2 || >= 24.15;
• Scripts: nyc → c8, added pretest, removed test:ci

Related Issue

• semantic-release/semantic-release#2133
• semantic-release/semantic-release#4032

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

v9.0.1

Compare Source

Bug Fixes

• deps: update dependency execa to v5 (#​228) (f536d60)

v9.0.0

Compare Source

chore

• require Node.js >=10.18 (4016fcc)

BREAKING CHANGES

• Require Node.js >= 10.18

v8.0.0

Compare Source

Bug Fixes

• package: update execa to version 4.0.0 (9c1dc67)
• include deleted files in release commit (f59d20c)
• package: update aggregate-error to version 2.0.0 (3eb8f60)
• package: update execa to version 2.0.2 (9404d44)
• package: update execa to version 3.0.0 (e6af5b4)
• look for modified fiels to commit only if there files matching the globs (d97c030)
• update globby to latest version (9e2b2e5)

Features

• require Node.js >=10.13 (81955b8)
• require Node.js >=8.15 (15356b1)
• support branch parameter from semantic-release@​16.0.0 (02b1f6d)

BREAKING CHANGES

• Require Node.js >= 10.13
• Require Git 2.7.1 or higher
• Require Node.js => 8.15

---

Configuration

📅 Schedule: (UTC)

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

👻 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

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