chore(deps): update semantic-release monorepo to v11

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@semantic-release/git	10.0.1 → 11.0.1
@semantic-release/npm	9.0.1 → 11.0.3

---

Release Notes

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

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

v11.0.3

Compare Source

Bug Fixes

• deps: raised the minimum accepted range of npm to v10.5.0 (#​759) (a0313f8), closes semantic-release/semantic-release#3202

even though our existing range allowed anyone to update as soon as the new npm version was available, this will encourage being on a version that does not report the ip vulnerability a bit more forcefully

v11.0.2

Compare Source

Bug Fixes

• deps: update dependency npm to v10.2.5 (42b5dec)

v11.0.1

Compare Source

Bug Fixes

• deps: update dependency read-pkg to v9 (#​703) (6e84013)

v11.0.0

Compare Source

Bug Fixes

• deps: update dependency npm to v10 (819f257)

Features

• node-versions: raised the minimum required node version to v18.17 and dropped v19 support (6413130)

BREAKING CHANGES

• node-versions: node v18.17 is now the minimum required version and support for v19 has been dropped

v10.0.6

Compare Source

Bug Fixes

• deps: update dependency aggregate-error to v5 (#​676) (f2bc9e7)

v10.0.5

Compare Source

Bug Fixes

• deps: update dependency execa to v8 (#​659) (502d5ba)

v10.0.4

Compare Source

Bug Fixes

• deps: update dependency @​semantic-release/error to v4 (#​628) (53a1012)

v10.0.3

Compare Source

Bug Fixes

• deps: update dependency read-pkg to v8 (#​602) (aaddc5c)

v10.0.2

Compare Source

Bug Fixes

• deps: update dependency fs-extra to v11.1.1 (#​591) (31e0e27)

v10.0.1

Compare Source

Bug Fixes

• deps: update dependency execa to v7 (#​575) (4c11706)

v10.0.0

Compare Source

Bug Fixes

• aggregate-error: upgraded to the latest version (7285e05)
• deps: upgraded npm to v9 (2a79f80)
• execa: upgraded to the latest version (7c74660)
• normalize-url: upgraded to the latest version (b55bb01)
• remove support for legacy auth (51ab3c8)
• tempy: upgraded to the latest version of tempy (f1992a5)

Code Refactoring

• esm: converted the package to esm (2d8ff15)

Features

• node-versions: dropped support for node versions below v18 (aff3574)
• semantic-release-peer: raised the minimum peer requirement to the first version that supports loading esm plugins (22e70ad)

BREAKING CHANGES

• deps: the direct dependency on npm has been upgraded to v9. details of breaking changes
  can be found at https://github.com/npm/cli/releases/tag/v9.0.0
• semantic-release-peer: the required version of semantic-release has been
  raised to v20.1.0 in order to support loading of ESM plugins
• aggregate-error: due to the aggregate-error upgrade, thrown errors are no longer iterable, but instead list the errors under an errors property
• legacy authentication using NPM_USERNAME and NPM_PASSWORD is no longer supported. Use NPM_TOKEN instead.
• node-versions: node v18 is now the minimum required node version
• esm: @semantic-release/npm is now a native ES Module. It
  has named exports for each plugin hook (verifyConditions, prepare,
  publish, addChannel)

v9.0.2

Compare Source

Bug Fixes

• deps: update dependency fs-extra to v11 (7157d76)
• deps: update dependency npm to v9 (28265ec)
• deps: update dependency registry-auth-token to v5 (187671f)
• revert): "fix(deps: update dependency npm to v9" (#​561) (c28a848)

---

Configuration

📅 Schedule: (in timezone Europe/Paris)

• Branch creation
  • "after 4pm on friday,before 9am on monday,every weekend"
• 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 these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[netlify]

❌ Deploy Preview for algolia-ga-actions-netlify failed.

Name	Link
🔨 Latest commit	329a83c
🔍 Latest deploy log	https://app.netlify.com/sites/algolia-ga-actions-netlify/deploys/65e2632cb3e9360008252a8d

[github-actions]

Check your created Crawler

Check your created index on your Algolia Application

[netlify]

❌ Deploy Preview for algolia-ga-actions-netlify failed.

Name	Link
🔨 Latest commit	dbead27
🔍 Latest deploy log	https://app.netlify.com/projects/algolia-ga-actions-netlify/deploys/6a777a6e04fa0000086cd242

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 duplication

Metric	Results
Duplication	0

View in Codacy

_{TIP This summary will be updated as you push new changes.}