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

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@semantic-release/changelog	6.0.3 → 7.0.0
@semantic-release/git	10.0.1 → 11.0.0

---

Release Notes

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

v7.0.0

Compare Source

Features

• ES Module (#​414) (e154214)

BREAKING CHANGES

• @semantic-release/changelog 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/changelog is now
  v20.1.0

Other Notable Changes

• Replaced xo with prettier with default configuration; following
  newly established convention
• Replaced nyc with c8 for code coverage
• Replaced lodash with lodash-es for proper esm support

Related Issue

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

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

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

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • Monday through Friday (* * * * 1-5)
• 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

npm warn cli npm v12.0.1 does not support Node.js v22.18.0. This version of npm supports the following node versions: `^22.22.2 || ^24.15.0 || >=26.0.0`. You can find the latest version at https://nodejs.org/.
npm warn Unknown env config "store". This will error in a future major version of npm. See `npm help npmrc` for supported config options.
npm error code EBADENGINE
npm error engine Unsupported engine
npm error engine Not compatible with your version of node/npm: @semantic-release/changelog@7.0.0
npm error notsup Not compatible with your version of node/npm: @semantic-release/changelog@7.0.0
npm error notsup Required: {"node":"^22.22.2 || >=24.15"}
npm error notsup Actual:   {"node":"v22.18.0","npm":"12.0.1"}
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-07-27T12_08_50_002Z-debug-0.log

[netlify]

❌ Deploy Preview for doist-typist failed.

Name	Link
🔨 Latest commit	40b7da8
🔍 Latest deploy log	https://app.netlify.com/projects/doist-typist/deploys/6a674a5b18f86d0008870db1

[doistbot]

Renovate bumps @semantic-release/changelog and @semantic-release/git to their latest majors — the project is already ESM and on semantic-release v25, so the breaking ESM-only change is fully compatible.

Few things worth tightening:

• package-lock.json still pins the old versions, but CI runs npm ci, which fails when the lockfile doesn't match package.json. Run npm install and commit the regenerated lockfile.

_{Share Feedback • Review Logs}

[doistbot]

package-lock.json still pins @semantic-release/changelog 6.0.3 and @semantic-release/git 10.0.1 (see the node_modules/@semantic-release/changelog and node_modules/@semantic-release/git entries), so it's out of sync with these bumped versions. CI uses npm ci (.github/workflows/check-ci-validation.yml, publish-package-release.yml), which fails when package.json and package-lock.json disagree. Run npm install and commit the regenerated lockfile.

[rfgamaral]

Closing in favour of #1442, which keeps Renovate on @semantic-release/changelog v6 and @semantic-release/git v10.

Both majors require Node ^22.22.2 || >=24.15, above the 24.13.0 this repository targets to stay in sync with its consumers. With engine-strict=true, npm ci fails outright on them, which is also why the lockfile could not be regenerated here.