WordPress 7.2, scheduled for December 8, 2026, will ship with jQuery Migrate 3.6.0. The core team announced the change on November 17, on the Make WordPress Core blog, as the first step in replacing jQuery 3 with jQuery 4. jQuery itself stays at 3.7.1 in this release, according to script-loader.php in the development repository.
The core team's plan across three releases
The announcement lays out three stages:
- In WordPress 7.2 (December 8), jQuery Migrate 3.6.0, so theme and plugin authors see warnings about features that no longer exist in jQuery 4.
- In WordPress 7.3, an update to the latest jQuery and jQuery Migrate, plus jQuery UI and other libraries that depend on jQuery. The post calls this step tentative and dependent on test results.
- At the end of 2027 (WordPress 7.5 or 7.6), jQuery Migrate stops being enabled by default, also subject to testing and to research on the impact on the ecosystem.
jQuery 4.0.0 came out in January 2026, and version 4.1.0 was published on npm on November 17. The last major jQuery upgrade in WordPress, to jQuery 3, was spread over several releases in 2020, and its final step, disabling Migrate by default, never happened. This time the schedule puts that step in writing from the start.
Who needs to look at this
jQuery Migrate is a compatibility layer: it restores APIs that jQuery removed and, in its development build, logs every use of a removed or deprecated API to the browser console. While it is loaded, old code tends to keep working, and the risk concentrates on the moment it is no longer enabled by default.
The sites that depend on it most are those with a custom theme or plugins written years ago, customized admin screens, and commercial plugins nobody updates anymore. The Migrate 3.x warning list shows the kind of code involved: jQuery.isArray, jQuery.trim, jQuery.parseJSON, jQuery.type, jQuery.isFunction, jQuery.now, .bind() and .unbind(), plus unitless numbers passed to .css().
Agencies and teams that maintain many WordPress sites are the most exposed, because the problem repeats for every theme and plugin combination.
What to do before 7.3
Nothing should break on December 8 because of this: jQuery stays on the 3.x series and Migrate is still active. What changes is that there is now an official tool to measure the size of the problem.
The practical detail is that the minified Migrate build, the one running in production, does not show warnings. WordPress loads the development files when the SCRIPT_DEBUG constant is turned on in wp-config.php. So the audit has to happen on a staging environment running 7.2 (RC1 is already available) with SCRIPT_DEBUG enabled, browsing the site and the admin and recording the JQMIGRATE warnings in the console, per theme and per plugin.
With that list, the decision gets concrete: fix your own code, push the commercial plugin vendor, or replace the abandoned plugin. It is the same choice described in a supported version still calls for a migration decision: the real deadline is the end of 2027, but fixing gets more expensive if the audit only starts after Migrate has been turned off.
If you update WordPress automatically, test 7.3 on staging before rolling it out, since it may bring jQuery 4 and a new jQuery UI in the same release.
What is still undecided
The 7.3 release date has not been announced, and whether jQuery 4 lands in it depends on testing. The post does not say which jQuery 4 version will be used. Disabling Migrate is planned for 7.5 or 7.6, without a date, and depends on impact research that has not been published yet. There is also no information so far about an official way to turn Migrate back on once it is off by default. Progress is tracked in ticket 60478 on the WordPress Trac.
If your company is weighing something similar, reach me on LinkedIn or WhatsApp.
References
- Preparing for jQuery 4 with WordPress 7.2 (Make WordPress Core)
- WordPress 7.2 Release Candidate 1 (WordPress News)
- Updating jQuery version shipped with WordPress (Make WordPress Core, 2020)
- jQuery Migrate: README
- jQuery Migrate 3.x: list of warnings
- script-loader.php in the wordpress-develop repository
- jquery on npm (version history)