chore(deps): update wordpress monorepo (major)

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@wordpress/eslint-plugin (source)	^22.22.0 → ^25.0.0
@wordpress/scripts (source)	^30.27.0 → ^32.0.0

---

Release Notes

WordPress/gutenberg (@​wordpress/eslint-plugin)

v25.0.0

Compare Source

Breaking Changes

• Upgraded to ESLint v10 with flat config format. The plugin now exports flat config arrays instead of eslintrc objects. Consumers must migrate from .eslintrc.* files to eslint.config.mjs. See the migration guide for details.
• The minimum required ESLint version is now ^9.0.0 || ^10.0.0.
• Upgraded eslint-plugin-import to v2.31+ (wrapped with fixupPluginRules for flat config compatibility).
• Upgraded @typescript-eslint/* from v6 to v8 (via the unified typescript-eslint package).
• Replaced eslint-plugin-eslint-comments with @eslint-community/eslint-plugin-eslint-comments. Rule prefixes changed from eslint-comments/* to @eslint-community/eslint-comments/*.

New Features

• Added @wordpress/eslint-plugin/eslintrc entry point — a compatibility wrapper for ESLint v9 consumers still using .eslintrc.* files. This is deprecated and will be removed in a future major version.
• Configs are now exported as flat config arrays (e.g., wordpress.configs.recommended returns an array of config objects suitable for spreading into eslint.config.mjs).

Enhancements

• Disabled the jsx-a11y/heading-has-content rule in the recommended configuration, which reports many false positives when heading elements are passed via a render prop (#​77073).

v24.5.0

Compare Source

v24.4.0

Compare Source

New Features

• Added no-dom-globals-in-module-scope, no-dom-globals-in-constructor, no-dom-globals-in-react-cc-render, and no-dom-globals-in-react-fc rules to prevent DOM global usage in SSR-unsafe contexts, replacing the unmaintained eslint-plugin-ssr-friendly package (#​76508).
• Added use-recommended-components rule to encourage the use of recommended UI components in a WordPress environment (#​76222).
• Added no-unmerged-classname rule to flag components that set an explicit className while spreading rest props without destructuring and merging the incoming className (#​76458).

Enhancements

• The no-unknown-ds-tokens rule now reports bare --wpds-* tokens not wrapped in var(), which would silently miss build-time fallback injection.
• The no-setting-ds-tokens rule now checks all object property keys, not just those inside JSX style attributes (#​76212).

v24.3.0

Compare Source

New Features

• Added no-ds-tokens rule to disallow usage of Design System token CSS custom properties (--wpds-*).

Enhancements

• The no-unknown-ds-tokens rule now checks all string literals and template literals, not just JSX style attributes. It also reports dynamically constructed --wpds-* token names.

v24.2.0

Compare Source

v24.1.0

Compare Source

Enhancements

• The dependency-group rule now accepts an optional "never" mode to forbid dependency group comments.

v24.0.0

Compare Source

Breaking Changes

• Updated recommended ruleset to enforce import/no-unresolved for @wordpress/ packages. These packages were previously exempted from the rule. (#​72978)
• Removed default configuration of import/internal-regex to classify @wordpress/ packages as internal. From the perspective of an external consumer of this package, @wordpress/ packages should be considered external. (#​72978)

New Features

• Added no-setting-ds-tokens rule to disallow setting Design System token CSS custom properties (--wpds-*). (#​74325)
• Added no-unknown-ds-tokens rule to disallow unknown Design System tokens. (#​74325)
• Added components-no-missing-40px-size-prop rule to opt-in to the new 40px default size for components from the @wordpress/components package. (#​74611)
• Added components-no-unsafe-button-disabled rule to ensure that buttons from the @wordpress/components package are accessible when disabled. (#​74611)

Enhancements

• The dependency-group rule is not recommended anymore. (#​73616)

v23.0.0

Compare Source

WordPress/gutenberg (@​wordpress/scripts)

v32.0.0

Compare Source

Breaking Changes

• The bundled eslint dependency has been upgraded from v8 to v10.
• The lint-js script now uses flat config (eslint.config.*) by default. Legacy .eslintrc.* files are still detected as a fallback, but this support is deprecated and will be removed in a future version.
• The default config shipped with wp-scripts has changed from config/.eslintrc.js to config/eslint.config.cjs.

v31.8.0

Compare Source

v31.7.0

Compare Source

v31.6.0

Compare Source

v31.5.0

Compare Source

v31.4.0

Compare Source

v31.3.0

Compare Source

Internal

• The bundled eslint dependency has been updated from ^8.3.0 to ^8.57.1 (#​74316).

v31.2.0

Compare Source

v31.1.0

Compare Source

v31.0.0

Compare Source

Breaking Changes

• The lint-js script now includes .cjs, .mjs, .cts, and .mts as default extensions to lint. This is considered a breaking change because the script may now surface lint errors in your project which would not have been previously identified.

---

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

npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: wp-stream@undefined
npm error Found: eslint@8.57.1
npm error node_modules/eslint
npm error   peer eslint@"^7.5.0 || ^8.0.0 || ^9.0.0" from @babel/eslint-parser@7.25.7
npm error   node_modules/@babel/eslint-parser
npm error   peer eslint@"^6.0.0 || ^7.0.0 || >=8.0.0" from @eslint-community/eslint-utils@4.4.0
npm error   node_modules/@eslint-community/eslint-utils
npm error     @eslint-community/eslint-utils@"^4.4.0" from @typescript-eslint/utils@6.21.0
npm error     node_modules/@typescript-eslint/utils
npm error       @typescript-eslint/utils@"6.21.0" from @typescript-eslint/eslint-plugin@6.21.0
npm error       node_modules/@typescript-eslint/eslint-plugin
npm error         peerOptional @typescript-eslint/eslint-plugin@"^5.0.0 || ^6.0.0 || ^7.0.0" from eslint-plugin-jest@27.9.0
npm error         node_modules/eslint-plugin-jest
npm error       1 more (@typescript-eslint/type-utils)
npm error     @eslint-community/eslint-utils@"^4.2.0" from eslint@8.57.1
npm error     1 more (@typescript-eslint/utils)
npm error   14 more (@typescript-eslint/eslint-plugin, ...)
npm error
npm error Could not resolve dependency:
npm error dev @wordpress/eslint-plugin@"^25.0.0" from the root project
npm error
npm error Conflicting peer dependency: eslint@10.2.0
npm error node_modules/eslint
npm error   peer eslint@"^9.0.0 || ^10.0.0" from @wordpress/eslint-plugin@25.0.0
npm error   node_modules/@wordpress/eslint-plugin
npm error     dev @wordpress/eslint-plugin@"^25.0.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-04-16T09_26_40_868Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-04-16T09_26_40_868Z-debug-0.log