WordPress 7.2: Release Date, Features, and What to Test

WordPress 7.2 is scheduled to ship on December 8, 2026. Beta 1 landed October 20, and the first release candidate follows on November 17.

The headline items are a new default theme called Ipsum, a suggestion mode for Notes, a Secrets API for storing credentials, and form styling in Global Styles. Nothing is locked until RC 1, though. The core team only ships roadmap items that are "reasonably ready."

Release schedule

Milestone	Date	What happens
Beta 1	October 20	Feature freeze, testing starts
Betas 2–4	October 27, November 3, November 10	Bug fixes
RC 1	November 17	Field Guide out, hard string freeze
RC 2–3	November 24, December 1	Final fixes
Dry run	December 7	24-hour code freeze
Release	December 8	WordPress 7.2 ships

Dates come from the official 7.2 release page. The earlier call for volunteers gave a December 8 to 10 window, so a day of slip wouldn't be a surprise. Matt Mullenweg is release lead, David Baumwald handles release coordination, and George Mamadashvili and Peter Wilson are tech leads.

What's new in WordPress 7.2

The full list is in the Roadmap to 7.2. These are the changes most site owners and developers will notice.

Ipsum, the new default theme

Ipsum is a minimal, blank-canvas blog theme, and the first default theme in years without a year in its name. Expect a plainer starting point than Twenty Twenty-Five.

Notes: suggestion mode and reactions

Notes are block-level comments on a draft. Suggestion mode would let editors propose changes the author accepts or rejects, like tracked changes in a word processor. Emoji reactions and a toolbar shortcut for adding a note are planned too. Suggestion mode is still a large change in review, so the smaller Notes updates could ship without it.

Secrets API and application password alerts

• Application passwords: you'll get an email when a new one is added to your account. That's a useful tripwire for account takeovers.
• Secrets API: a standard place in core to store credentials like API keys, instead of every plugin rolling its own (often plain options). WP-CLI support comes first; a settings screen is planned for 7.3.
• Sudo mode (re-entering your password before risky admin actions) is on the list but has no public proposal yet, so it may slip to 7.3.

Form styling in Global Styles

Global Styles gets UI for styling buttons, text inputs, selects, and labels, including hover and focus states. Block settings may also start showing the value a block inherits from Global Styles, with a way to reset an override. That design is still open.

New and updated blocks

• Description List: a block for <dl>, <dt>, and <dd> markup. Good for glossaries and spec sheets.
• Table of Contents: moves to server-side rendering and is set to become stable.
• Icon block: search icons by keyword, not just by label.
• Interactivity API: a new data-wp-html directive for rendering trusted markup, plus router fixes.

Admin, accessibility, and performance

• Clearer error messages with a copy button.
• Admin notices that screen readers announce properly and that can be dismissed with the keyboard.
• Automated axe-core accessibility checks in core's test suite.
• An "On This Day" dashboard widget, back for another try after being pulled from 7.1.
• Admin script and style concatenation replaced with prefetching.

AI work, mostly in the AI plugin

Most AI work this cycle lives in the official AI plugin, not core. The plan adds read-only abilities for media, taxonomies, and comments, and puts the MCP Adapter in the Plugin Directory. MCP (Model Context Protocol) is the standard that lets AI tools talk to your site.

What's not coming in 7.2

• Real-time collaboration: left out and being reworked.
• React 19: far along, but unlikely to fully land.
• Secrets settings screen: planned for 7.3.
• Extensible Site Editor: groundwork continues through 7.3.

How to test WordPress 7.2 before release

Use a staging copy, never a live site.

1. Make a staging copy and take a fresh backup.
2. Install the WordPress Beta Tester plugin. Go to Tools → Beta Testing, pick the bleeding edge channel and the beta/RC stream, then update from Dashboard → Updates.
3. Or use WP-CLI on staging: wp core update --version=7.2-beta1
4. Click through forms, custom blocks, and any admin screens your plugins add.
5. Check front-end buttons and inputs, since the new form styling touches them.
6. Report bugs on Core Trac or in the Gutenberg GitHub repo.

Should you update on release day?

Take a full backup first either way, as the official Updating WordPress guide recommends.

Your site	When to update	Why
Personal blog, few plugins	Release week	Low risk, and a backup covers you
Business site you manage	After testing on staging	Forms and checkout are where updates break things
Client sites	After the first point release	Plugins have time to ship fixes
Any site, security release	Right away	Security fixes close known holes

---

AI assisted with drafting this post. I reviewed and edited it before publishing.

Originally published on matthummel.com.