WordPress 7.1, named “Mary Lou,” was released on August 19, 2026, with a 7.1.1 maintenance release following in September. It is a smaller release than 7.0 was, which is good news if you are looking at your update queue in October and wondering whether this is a job for now or for December.
Here is what actually changed, and how to think about the timing.
The question in October is not whether an update is good. It is whether you have enough runway left to discover what it broke.
Primo Collab
What shipped
New blocks in core. Tabs arrived as a proper set: Tabs, Tab List, Tab Panel, and Tab Panels. There is also a Playlist block with an accompanying Playlist Track block for audio content. Both of these are things people previously reached for a plugin to do.
The Abilities API became real structure. In 7.0 this was foundational plumbing. In 7.1 it is formalised into actual classes and REST endpoints, which matters if you are connecting AI tools to your site, and matters not at all if you are not.
The AI client expanded. Adapter classes, an HTTP client with caching, and a prompt builder. Again: infrastructure. Nothing activates on its own, and nothing connects anywhere until an administrator sets it up.
An icon collections registry, plus block states support and some media handling improvements including web worker support for processing.
What this means for a typical business site
Honestly: less than the release notes suggest. For most small business sites running a normal theme and a handful of plugins, 7.1 is a maintenance update with two genuinely useful additions.
The Tabs blocks are the one thing likely to matter day to day. Tabbed content on product pages, service pages, and FAQs is common, and it has historically meant either a page builder or a dedicated plugin. Having it in core means one less dependency, which is a real reduction in long-term risk even though it is a small one today.
Everything else is either invisible to you or only relevant if you are deliberately building on the AI features.
Should you update in October?
Yes, and early in the month rather than late. The reasoning is about sequencing rather than the release itself.
A major version update touches the block editor, block rendering, and APIs that plugins depend on. Most problems it causes are not immediate: a template that renders slightly differently, a plugin that throws an error on one specific page, a layout that shifts on mobile. These surface over days of ordinary traffic.
If you update in early October, you have six or seven weeks of normal traffic to find those problems. If you update in mid November, you have days, and you are looking for them during the period when you least want to be looking for anything.
How to do it without drama
- Update on a staging copy first. This is the whole game. If you do not have staging, that is worth solving before this update rather than after.
- Check your highest-value pages specifically. Homepage, main service or collection pages, product pages, and every form and checkout step.
- Check on a phone, not just a resized desktop browser.
- Confirm your plugins have declared compatibility. Anything that has not been updated since before August deserves particular attention.
- Take a backup you have actually verified before pushing to live. Not “backups are running.” A restore you have tested.
- Then push to live, and check the same list again.
If you cannot update before your freeze
That is a legitimate position, particularly for a store heading into a heavy Q4. If you decide to defer, make it an explicit decision with a date attached rather than a thing that quietly does not happen:
- Note which version you are on and why you deferred.
- Keep applying security patches regardless. Deferring a feature release is reasonable; deferring security fixes is not.
- Schedule the update for the first week of December, when your freeze lifts.
The mistake to avoid
Skipping major versions indefinitely because each individual update feels risky. The risk does not stay flat: it compounds. Updating from 7.1 to 7.2 next year is a routine job. Updating from 6.8 to 7.2 after skipping four releases is a project, with more places to break at once and less ability to tell which change caused what. The safest position is boringly current, reached through small steps taken during quiet months.