chore(deps): bump @wordpress/eslint-plugin from 24.5.0 to 25.4.0 in /packages/eslint-config

[dependabot]

Bumps @wordpress/eslint-plugin from 24.5.0 to 25.4.0.

Changelog

Sourced from @​wordpress/eslint-plugin's changelog.

25.4.0 (2026-06-10)

25.3.0 (2026-05-27)

25.2.0 (2026-05-14)

New Features

• Added no-non-module-stylesheet-imports rule to prevent importing non-module stylesheets from JavaScript files (#77984).

25.1.0 (2026-04-29)

New Features

• Added use-import-as rule to enforce configured aliases for selected named imports and direct unlock( privateApis ) destructuring (#77389).
• Added no-unsafe-render-order rule to flag unsafe render-prop composition with VisuallyHidden and Link/Text (#77428).

Enhancements

• Improved the Design System token lint rules to recognize CSS declaration strings more accurately, avoiding false bare-token reports for declarations while still flagging invalid token assignments and unknown token names (#77384).
• Update use-recommended-components rule to prefer VisuallyHidden from @wordpress/ui over @wordpress/components (#77575).

25.0.0 (2026-04-15)

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 (#76654).
• The minimum required ESLint version is now ^9.0.0 || ^10.0.0 (#76654).
• Upgraded eslint-plugin-import to v2.31+ (wrapped with fixupPluginRules for flat config compatibility) (#76654).
• Upgraded @typescript-eslint/* from v6 to v8 (via the unified typescript-eslint package) (#76654).
• Replaced eslint-plugin-eslint-comments with @eslint-community/eslint-plugin-eslint-comments. Rule prefixes changed from eslint-comments/* to @eslint-community/eslint-comments/* (#76654).

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 (#76654).
• 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) (#76654).

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

Commits

• 6da9506 chore(release): publish
• 6afbb15 Update changelog files
• e816d95 Merge changes published in the Gutenberg plugin "release/23.4" branch
• 6237509 Update changelog files
• d653c5f chore(release): publish
• 065fa3b Update changelog files
• f63ca66 Merge changes published in the Gutenberg plugin "release/23.3" branch
• 7f4e229 Update changelog files
• b5afac3 Merge changes published in the Gutenberg plugin "release/23.3" branch
• fee7eec Update changelog files
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[changeset-bot]

⚠️ No Changeset found

Latest commit: d261484

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR