WordPress 7.2 Release Date – Release Squad & Launch Date

WordPress 7.2 is the third and final major WordPress release of 2026, and it is scheduled to launch on December 9, 2026, live during Matt Mullenweg’s annual State of the Word keynote. The release squad has been announced, the roadmap is public, and trunk has been in alpha since August 10.

If you run a WordPress site, build plugins or themes, or manage client websites, this is the release to start planning for now. In this guide, we cover the official WordPress 7.2 release date, the full release squad, the beta and RC schedule, the features on the roadmap (including the brand-new default theme, Ipsum), and a practical checklist to get your site ready before update day.

WordPress 7.2 at a Glance

When Is WordPress 7.2 Coming Out?

The official target for WordPress 7.2 is Wednesday, December 9, 2026. The Make WordPress Core team has published a release window of December 8–10 to leave room for small adjustments, but the plan is to ship it on stage during State of the Word.

This follows a pattern the project started last year. WordPress 6.9 was released live during the 2025 State of the Word in San Francisco, and 7.1 was timed to launch at WordCamp US 2026 in August. Tying major releases to big community events gives the launch more visibility, but it also makes the date less flexible. The core team has already noted that the December slot is tight because of global holidays, end-of-year time off, and the long-standing rule of never shipping a major release on a weekend.

In short: expect December 9, but keep an eye on the Make Core blog in case the date moves by a day.

WordPress 7.2 Release Squad

The WordPress 7.2 release squad was announced on the Make WordPress Core blog in September 2026 after an open call for volunteers. According to the announcement, more people volunteered than there were roles available. Here is the full team:

A few things stand out about this squad:

• Matt Mullenweg is back as release lead. He sat out WordPress 7.0 (led by Matías Ventura) and 7.1 (led by Anne McCarthy), so 7.2 marks his return to the role.
• The squad is small and focused. Since WordPress 6.7, the project has used a leaner release squad. Instead of filling every possible role, Make Team representatives coordinate work inside their own teams (docs, polyglots, accessibility, and so on).
• There are dedicated default theme leads. Because 7.2 ships with a new default theme, it has its own design and development leads.
• Test leadership has a strong community presence. Md Noruzzaman, one of the test leads, is a well-known contributor from Bangladesh, which is great to see for the South Asian WordPress community.

WordPress 7.2 Release Schedule

Here is the full development timeline, from alpha through the final release. Each beta and RC has a short window rather than a fixed day, so the squad can adjust as needed.

Beta 1 is the feature freeze point. After that, no new enhancements get committed; the focus shifts to bug fixing, testing, and dev notes. If you are a plugin or theme developer, Beta 1 is the moment to start testing seriously.

Expected Features in WordPress 7.2

The official “Roadmap to 7.2” post was published on September 18, 2026. As always, roadmap items are being actively worked on, but not every item is guaranteed to make the final release. Here are the headline areas.

1. A New Default Theme: Ipsum

WordPress 7.2 is set to ship with a new default theme called Ipsum. It is a deliberately minimal, “blank canvas” blog theme designed for people who want to build their own design on top of it. The proposal calls for WCAG AA color contrast throughout, which is a nice win for accessibility.

The bigger news is the name. Ipsum ends 16 years of calendar-based theme names. There will be no “Twenty Twenty-Six”. Default themes will now get individual names and will be released when the design calls for it, not on a fixed annual schedule. An earlier, more expressive proposal called Mētis was replaced by Ipsum but remains available as a separate theme.

2. Notes Get Suggestion Mode and Reactions

Notes (block-level commenting inside the editor) has grown steadily since WordPress 6.9, picking up @mentions and rich text along the way. In 7.2, the centerpiece is suggestion mode: you can propose edits that the author accepts or rejects, similar to “Suggesting” in Google Docs. Emoji reactions and better discoverability are also on the list. For agencies and content teams that review drafts with clients, this could remove a lot of back-and-forth over email.

Note that full real-time collaborative editing is not part of 7.2. The core team has said it needs more time for architectural decisions, so it has been left off the roadmap entirely.

3. Security Hardening: Sudo Mode and a Secrets API

By WordPress standards, 7.2 is a security-heavy release:

• Sudo mode asks you to re-authenticate before performing sensitive admin actions, even if you are already logged in.
• A new Secrets API gives plugins a first-class, standard way to store credentials such as API keys and tokens, with WP-CLI support.
• Application Passwords improvements include better local/HTTPS environment detection, user notifications, and safer default role handling.

For plugin developers, the Secrets API is the big one. Plugins that connect to external services (Google Drive, Dropbox, payment gateways, CRMs) currently all invent their own way of storing tokens. A shared core API should make that safer and more consistent. We are already looking at how to adopt it in CodeConfig plugins such as Integration for Google Drive and Integrate Dropbox, both of which store OAuth tokens.

4. An Extensible Site Editor for Plugin Authors

WordPress 7.2 introduces a server-side view-config endpoint that lets plugins register their own screens and settings inside the Site Editor for the first time. Along with this, DataViews and DataForms give third parties control over which fields appear and which layouts are available for any entity. This means plugin settings pages can finally feel native to the modern WordPress admin instead of living in a separate, old-style screen.

5. Blocks, Design Tools, and Global Styles

• A new Description List block.
• A stabilized Table of Contents block.
• More robust Global Styles for form elements and block states (hover, focus, and so on).
• Responsive styling for third-party blocks with custom controls.

6. Accessibility: Dashicons Replaced With SVG Icons

The old Dashicons icon font is being replaced with accessible SVG icons. If your plugin or theme relies on Dashicons in the admin, test your UI carefully during the beta period.

7. AI Stays in the AI Plugin (For Now)

AI features such as MCP access, agent identity, embeddings, and streaming responses remain in the separate AI plugin. The core team wants to see real adoption before moving them into core.

What WordPress 7.2 Means for Developers and Site Owners

For plugin and theme developers

• Start testing against trunk or Beta 1 as soon as it is out (October 20–22).
• Check any admin UI that uses Dashicons.
• Plan how you will adopt the Secrets API if your plugin stores credentials.
• Explore registering settings screens in the Site Editor via the new endpoint.
• Update the Tested up to header in your readme once you have confirmed compatibility.
• Watch for dev notes on the Make Core blog during beta, and the Field Guide at RC1.

For site owners and agencies

• Do not update production on release day. Test on a staging site first.
• Update your client documentation if it names Twenty Twenty-Five as the default theme.
• Set expectations: real-time collaboration is still not in core.
• Make sure you are already on the latest 7.1.x release. WordPress 7.1.2 was released on September 22, 2026 to patch a critical vulnerability, so update now if you have not.

How to Prepare Your Site for WordPress 7.2

1. Take a full backup of files and database before any major update.
2. Create a staging copy of your site and test 7.2 there first.
3. Update plugins and themes to their latest versions before upgrading core.
4. Check your PHP version with your host and make sure it meets current WordPress recommendations.
5. Test critical flows: checkout, forms, logins, membership areas, and any third-party integrations.
6. Wait for 7.2.1 if your site is business-critical. Minor bug-fix releases usually follow within a few weeks.

Need help testing plugin compatibility or upgrading a client site safely? The CodeConfig team builds and maintains WordPress plugins every day, and we are already testing our own products against WordPress 7.2. You can also book a free 30-minute consultation to talk through your upgrade plan.

Final Thoughts

WordPress 7.2 is scheduled for December 9, 2026, with Matt Mullenweg leading a small, focused release squad. It brings a brand-new default theme (Ipsum), suggestion mode for Notes, meaningful security upgrades like sudo mode and the Secrets API, and a more extensible Site Editor for plugin authors. It is not the release where real-time collaboration or AI lands in core, but it is a solid, security-focused way to close out 2026.