WordPress 7.2 Beta 1 has been available for download since October 20, 2026, with Beta 2
planned for October 27 and a final release targeted for December 8. This release lays the
groundwork for a Secrets API to store credentials, reworks the Notes feature introduced in
6.9, and permanently drops load-scripts.php and load-styles.php, both inherited from
WordPress 2.3.
A Secrets API to get credentials out of plain code
Core had never offered a standard mechanism for storing sensitive credentials: third-party
API keys, tokens, connection secrets. The Secrets API introduced in Beta 1 fills that gap and
should, over time, reduce the practice of dropping those values in plain text inside
wp-config.php or in the database options table. The development team is asking
plugin authors to test integrating their own credentials with this API now, ahead of the final
release, a push that builds on the principles already laid out in a
minimal WordPress hardening baseline.
Notes: reactions, anchored on the canvas
Notes, which shipped in 6.9 as a commenting system layered on content, gain emoji reactions
and a dedicated toolbar icon. Notes are now anchored directly on the editor canvas rather than
living in a separate panel, bringing editorial discussion closer to the block it concerns.
Extended responsive controls, richer global styles
Per-breakpoint settings, introduced in 7.1,
now cover more blocks in this beta: Gallery columns, cropping and aspect ratio can all vary by
screen size. On the Global Styles side, a “Customized” filter helps surface blocks with
modified styles, and text-shadow controls make their debut, available both in block settings
and as theme.json presets.
| Feature | WordPress 7.1 | WordPress 7.2 Beta 1 |
|---|---|---|
| Credential storage | No native mechanism | Secrets API |
| Notes | Comments on content | Emoji reactions, anchored on canvas |
| Responsive controls | A handful of blocks | Extended (Gallery, cropping, ratio) |
| load-scripts.php / load-styles.php | Active | Removed |
| Suggestion mode | Not planned | Pushed to version 7.3 |
The end of legacy script concatenation
The most structurally significant change for theme and plugin maintainers is the removal
of load-scripts.php and load-styles.php, closing more than ten Trac tickets that had been open
for years. This concatenation mechanism, designed back when cutting the number of HTTP
requests mattered more than anything else, had been losing relevance since the widespread
adoption of HTTP/2 and modern bundlers.
wp core update --version=7.2-beta1 --force
wp core version
wp plugin list --status=active
Beta 1 closes more than ten Trac tickets by outright removing load-scripts.php and load-styles.php, a concatenation system inherited from WordPress 2.3.
Suggestion mode waits for the next release
Described by the Automattic team as the centerpiece of editorial collaboration, suggestion
mode, meant to let contributors propose edits to a post without applying them directly, has
once again slipped, this time to version 7.3. AI-related editor features, MCP access, agent
identity, embeddings, remain confined to the separate AI plugin and are not part of core.
environment, for example a
dedicated self-hosted test server,
specifically to validate plugin compatibility with the removal of load-scripts.php and
load-styles.php.
Key takeaways
WordPress 7.2 enters testing with a brand-new Secrets API, reworked Notes, and the removal
of a concatenation mechanism more than twenty years old. Suggestion mode, once billed as the
flagship feature, slips again on the calendar. The final release stays set for December 8,
2026, with Beta 2 expected on October 27.
I’m telling my clients to test their in-house extensions against this beta as soon as
possible, specifically because of the load-scripts.php removal: some older plugins, written
before webpack or Vite became standard on the admin side, still quietly depended on it. The
Secrets API, on the other hand, is the most welcome addition on my list: being able to store a
third-party API key cleanly without leaving it sitting in the options table was a clear gap in
core. — Simon Janvier
Further reading: the official announcement on wordpress.org.
