The final release is planned for December 8, 2026. Before then, the next milestone is Release Candidate 1, scheduled for November 17, 2026 at 15:00 UTC. If you maintain client sites, use the intervening weeks to find out what breaks.
Beta 5 is intended only for testing and development. Do not use it on production or mission-critical websites. Instead, try it on a local site or in a test environment.
What is new
- An email notification is sent when an application password is created, and it can be filtered or disabled with WordPress filters.
- A keyboard skip link appears when the toolbar shows before front-end content.
- Ipsum, the new default theme, gets another round of work on accessibility, block styles, patterns and stylesheets.
- All known WordPress compatibility issues with PHP 8.6 are resolved, but plugins and themes still need checking.
- Smaller fixes cover Notes reaction permissions, MP3 upload compatibility and automatic updates in Git worktree installations.
- Next on the schedule: Release Candidate 1 on November 17, 2026, then the final release on December 8, 2026.
Taken from the official update: wordpress.org [1]
Security and accessibility changes you can see
Introduced in WordPress 5.6, application passwords allow an app or script to sign in to a site without using the main account password. Before this change, WordPress did not email users when an application password was added to an account. Beta 5 now sends that notification. For agencies, clients will receive a message when a new credential is added, so it is worth explaining in advance what the email means. WordPress filters can be used to modify or disable the notification, which works for teams that intentionally create many of these credentials.
Fact checked on 12 Nov 2026 against core.trac.wordpress.org [2], wordpress.org [4]
The toolbar update benefits people who use a keyboard to navigate. A skip link now appears when the toolbar is displayed before front-end content. It does not affect wp-admin, and themes that lack wp_body_open support continue to behave as before. For older client themes, check the toolbar behavior for logged-in editors.
Fact checked on 12 Nov 2026 against core.trac.wordpress.org [3]
Beta 5 also makes accessibility improvements to Visual History. The official 7.2 roadmap calls this feature visual revisions, which allows editors to review changes across saved revisions and compare or restore them. The post does not specify the exact improvements.
Fact checked on 12 Nov 2026 against wordpress.org [1], make.wordpress.org [7]
Ipsum is planned as the new default theme, and existing sites keep theirs
According to the Make WordPress Core announcement, Ipsum is planned for inclusion with 7.2, and Beta 5 improves its accessibility, block styles, patterns and stylesheets. The post does not give the theme a separate release date, so it will come out with WordPress 7.2.
Fact checked on 12 Nov 2026 against wordpress.org [1], make.wordpress.org [5]
Installing 7.2 on an existing site does not change its active theme to Ipsum. WordPress documentation explains that a theme must be activated to become the current theme and that the default theme serves as a fallback if the active theme is lost or deleted. A client site will look the same unless you select Ipsum. For a new site, the guide to building a site with WordPress explains where the theme fits into a typical setup, while the WordPress page builders overview describes alternatives to the block editor.
Fact checked on 12 Nov 2026 against wordpress.org [6]
PHP 8.6 and the other fixes
WordPress 7.2 is intended to fully support PHP 8.6, which the post says is scheduled to be released on November 19, 2026. By Beta 5, all known compatibility issues in WordPress itself have been fixed. The post still asks users to confirm that their plugins and themes work with PHP 8.6 before upgrading. Since PHP 8.6 will not be released until November 19, those checks can start only after that date.
Fact checked on 12 Nov 2026 against wordpress.org [1]
This matters in practice to anyone using a page builder. A ready WordPress core does not guarantee that every add-on is ready, so testing a staging copy with the new PHP version is the safe way to check. Updating WordPress does not update the PHP version, which must be changed separately in your hosting settings.
Fact checked on 12 Nov 2026 against wordpress.org [1]
Notes lets people leave feedback on individual blocks. Users can resolve notes and edit or delete notes and replies. In 7.2, the feature adds a suggestion mode, emoji reactions and a block toolbar shortcut. Beta 5 improves permissions for those reactions. Other listed fixes improve MP3 upload compatibility and change automatic update behavior in Git worktree installations. The post identifies only that installation type for the final fix.
Fact checked on 12 Nov 2026 against wordpress.org [1], make.wordpress.org [8], make.wordpress.org [7]
How to test Beta 5
The post gives four ways to try the beta: use the WordPress Beta Tester plugin with the Bleeding edge channel and the Beta/RC Only stream, download it directly, use WP-CLI, or use WordPress Playground. The WP-CLI command is wp core update --version=7.2-beta5.
Fact checked on 12 Nov 2026 against wordpress.org [1]
The right choice depends on your needs. WordPress Playground runs in a browser without setup, making it a good fit for anyone who just wants to explore. The Beta Tester plugin works for a staging copy of a real site, since you can keep the site and switch to the beta channel.
Fact checked on 12 Nov 2026 against wordpress.org [1]
What the official notes do not say
- The post does not describe the exact accessibility refinements made to Visual History.
- The post does not say which plugins or themes work with PHP 8.6. It points to the Making WordPress Core blog for more detail in the coming days.
- The post does not explain the Notes permission, MP3 and Git worktree fixes beyond naming them and linking their Trac tickets.
How it helps: a freelancer who maintains WordPress sites for local businesses
The task. Before the final release, check whether a client's plugins and theme are compatible with WordPress 7.2 and PHP 8.6
- Copy the client site to a local site or staging environment, never the live site.
- Install and activate the WordPress Beta Tester plugin and select the Bleeding edge channel and the Beta/RC Only stream.
- Update the copy to WordPress 7.2 Beta 5 while it still runs the current PHP version, and click through the pages the client depends on.
- After PHP 8.6 is released on November 19, 2026, switch the staging copy to PHP 8.6 and click through the same pages again.
- Report any problem in the Alpha/Beta area of the support forums, or on WordPress Trac if you can write a reproducible bug report.
The result. You find out about compatibility problems before the December 8, 2026 release date, leaving time to fix them during the beta cycle.
Fact checked on 12 Nov 2026 against wordpress.org [1], make.wordpress.org [9]
Other ways to use it
After 7.2 becomes final, each new application password is expected to send the user an email, unless the agency filters or disables the email. Plan to explain the message to clients.
Fact checked on 12 Nov 2026 against core.trac.wordpress.org [2]
Related nvudev guides
Sources
- https://wordpress.org/news/2026/11/wordpress-7-2-beta-5/ (official update)
- https://core.trac.wordpress.org/ticket/63927
- https://core.trac.wordpress.org/ticket/66331
- https://wordpress.org/news/2020/12/simone/
- https://make.wordpress.org/core/2026/09/16/introducing-ipsum-the-new-default-theme/
- https://wordpress.org/documentation/article/work-with-themes/
- https://make.wordpress.org/core/2026/09/18/roadmap-to-7-2/
- https://make.wordpress.org/core/tag/notes/
- https://make.wordpress.org/core/2026/10/06/wordpress-7-2-release-party-schedule/
Facts in this article were checked against these sources on 12 Nov 2026. Product details change, so check the official page before you rely on them.