Lena Morita describes in a Dev Note on WordPress 7.2 a bug in the build tool @wordpress/build. Because of this bug, the styles of bundled package copies could influence each other. WordPress 7.2 ships with corrected packages and is scheduled for release on December 8, 2026.
Plugin authors whose plugins bring their own copies of the packages are affected first. Website operators notice it only indirectly, namely when a plugin with an older copy is running on their site.
What went wrong with the class names?
Some plugins ship @wordpress packages themselves instead of using the scripts loaded by WordPress. The styles of these packages use CSS modules, a technique that generates class names automatically. In the build tool, these names depended only on the file path and the class name, not on the content of the CSS.
As a result, two versions of the same component got the same class name even though their CSS was different. As an example, the Dev Note mentions a focus ring on all tabs over which the mouse pointer hovers. All versions released before the fix are affected.
Who needs to act before WordPress 7.2?
As of WordPress 7.2, the class names change as soon as the associated CSS changes. Two copies will therefore only have the same name if their CSS is identical. The packages shipped with 7.2 are already corrected, so older copies from plugins no longer collide with them.
What do you need to do before WordPress 7.2?
Dev Note from November 16, 2026, release of WordPress 7.2 planned for December 8
Which role applies to you?
You run a websiteCheck the site in a test environment, wait for plugin updates
Your plugin bundles @wordpress packagesSet minimum versions, release before 7.2
Your plugin loads wp-componentsDo nothing, WordPress 7.2 delivers the fix
You compile CSS modules yourself@wordpress/build 0.27.0 or newer, rebuild
The author does not publish a list of affected plugins.
Source: Make WordPress Core
Two older copies, on the other hand, can still interfere with each other, for example when two plugins bring different older versions of @wordpress/ui. The problem is therefore only solved once plugin authors update their copies.
According to the Dev Note, plugin authors who bundle packages should move to at least these versions and publish a new release before WordPress 7.2:
Package
Minimum version
@wordpress/ui
0.26.0
@wordpress/dataviews
22.0.0
@wordpress/admin-ui
3.1.0
@wordpress/grid
0.11.0
@wordpress/components
44.0.0
Plugins that compile CSS modules with @wordpress/build need version 0.27.0 or newer and a new build. Plugins that load @wordpress/components via the wp-components script do not need to do anything, because WordPress 7.2 brings the corrected version there.
What this means for you
As a website operator, you cannot change anything about the packages. Test WordPress 7.2 in advance in a test environment and never on the live site: According to the post on Beta 5, the beta is intended only for testing and development. It is best to click through the settings pages of your plugins there and watch out for tabs, tables, and buttons whose focus ring appears in the wrong place.
If you notice such anomalies, write to the plugin developer and refer to the Dev Note. It is best to apply the core update on the live site only once the vendors of your most important plugins have published their updates. The author does not list which plugins are affected.
For your own plugins, search the package.json for @wordpress/ui, dataviews, admin-ui, grid, and components. Raise the versions to at least the values from the table and publish the release before December 8.
Lena Morita published the Dev Note on November 16, 2026.