The WordPress coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:
Found a bugbugA bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority.?Create a ticket in the bug tracker.
The forth Release Candidaterelease candidateOne of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). (“RC4”) for WordPress 6.9 is ready for download and testing!
This version of the WordPress software is under development. Please do not install, run, or test this version of WordPress on production or mission-critical websites. Instead, it’s recommended that you evaluate RC4 on a test server and site.
Reaching this phase of the release cycle is an important milestone. While release candidates are considered ready for release, testing remains crucial to ensure that everything in WordPress 6.9 is the best it can be.
You can test WordPress 6.9 RC4 in four ways:
PluginPluginA plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party
Install and activate the WordPress Beta Tester plugin on a WordPress install. (Select the “Bleeding edgebleeding edgeThe latest revision of the software, generally in development and often unstable. Also known as trunk.” channel and “BetaBetaA pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process./RCrelease candidateOne of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). Only” stream).
Direct Download
Download the RC4 version (zip) and install it on a WordPress website.
Command Line
Use the following WP-CLI command: wp core update --version=6.9-RC4
The scheduled final release date for WordPress 6.9 is December 2, 2025. The full release schedule can be found here. Your help testing RC versions is vital to making this release as stable and powerful as possible. Please continue checking the Make WordPress Core blog for 6.9-related posts in the coming weeks for more information.
What’s in WordPress 6.9 RC4?
Get a recap of WordPress 6.9’s highlighted features in the Beta 1 announcement. Take a look at the WordPress 6.9 Field Guide. For more technical information related to issues addressed since RC3, you can browse the following links:
The following updates have been addressed since RC3:
#64305: Hidden async-upload field marked as required causes publishing to fail in the editor.
#64315: Running _wp_cron() during shutdown breaks sites using ALTERNATE_WP_CRON.
#64269: “Remove” button in Media Library gallery has a UIUIUser interface styling issue.
#41604:REST APIREST APIThe REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/. incorrectly returns success instead of an error when updating a non-existent setting.
WordPress is open sourceOpen SourceOpen Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. software made possible by a passionate community of people collaborating on and contributing to its development. The resources below outline various ways you can help the world’s most popular open source web platform, regardless of your technical expertise.
Get involved in testing
Testing for issues is crucial to the development of any software. It’s also a meaningful way for anyone to contribute.
Your help testing the WordPress 6.9 RC4 version is key to ensuring that the final release is the best it can be. While testing the upgrade process is essential, trying out new features is equally important. This detailed guide will walk you through testing features in WordPress 6.9. For those new to testing, follow this general testing guide for more details on getting set up.
If you encounter an issue, please report it to the Alpha/Beta area of the support forums or directly to WordPress Trac if you are comfortable writing a reproducible bugbugA bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. report. You can also check your issue against a list of known bugs.
For plugin and theme authors, your products play an integral role in extending the functionality and value of WordPress for all users.
Thanks for continuing to test your themes and plugins with the WordPress 6.9 beta releases. If you haven’t yet, make sure to conclude your testing and update the “Tested up to” version in your plugin’s readme file to 6.9.
If you find compatibility issues, please post detailed information to the support forum.
Test on your hosting platforms
Web hosts provide vital infrastructure for supporting WordPress and its users. Testing on hosting systems helps inform the development process while ensuring that WordPress and hosting platforms are fully compatible, free of errors, optimized for the best possible user experience, and that updates roll out to customer sites without issue.
WordPress 6.9 BetaBetaA pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 4 is ready for download and testing!
This version of the WordPress software is still under development. Please do not install, run, or test this version of WordPress on production or mission-critical websites. Instead, it’s recommended to test Beta 4 on a test server and site.
WordPress 6.9 Beta 4 can be tested using any of the following methods:
PluginPluginA plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party
Install and activate the WordPress Beta Tester plugin on a WordPress install. (Select the “Bleeding edgebleeding edgeThe latest revision of the software, generally in development and often unstable. Also known as trunk.” channel and “Beta/RCrelease candidateOne of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). Only” stream.)
The scheduled final release date for WordPress 6.9 is still December 2, 2025. The full release schedule can be found here. Your help testing Beta and RC versions is vital to making this release as stable and powerful as possible. Thank you to everyone who helps with testing!
The 6.9 Release Candidaterelease candidateOne of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). is still scheduled for Tuesday, November 11th, and the final release on December 2nd is still on track. As always, a successful release depends on your confirmation during testing. So please download and test!
How to test this release
Your help testing the WordPress 6.9 Beta 4 version is key to ensuring that the final release is the best it can be. While testing the upgrade process is essential, trying out new features is equally as important. This detailed guide will walk you through testing features in WordPress 6.9.
If you encounter an issue, please report it to the Alpha/Beta area of the support forums or directly to WordPress Trac if you are comfortable writing a reproducible bugbugA bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. report. You can also check your issue against a list of known bugs.
WordPress 6.9 BetaBetaA pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 is ready for download and testing!
This beta release is intended for testing and development only. Please do not install, run, or test this version of WordPress on production or mission-critical websites. Instead, use a test environment or local site to explore the new features.
How to Test WordPress 6.9 Beta 1
You can test WordPress 6.9 Beta 1 in any of the following ways:
WordPress Beta Tester PluginPluginA plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party
Install and activate the WordPress Beta Tester plugin on a WordPress install. Select the “Bleeding edgebleeding edgeThe latest revision of the software, generally in development and often unstable. Also known as trunk.” channel and “Beta/RCrelease candidateOne of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). Only” stream.
Command Line (WP-CLIWP-CLIWP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/https://make.wordpress.org/cli/)
Use this WP-CLI command: wp core update --version=6.9-beta1
The scheduled final release date for WordPress 6.9 is December 2, 2025. The full release schedule can be found here. Your help testing Beta and RC versions is vital to making this release as stable and powerful as possible. Thank you to everyone who contributes by testing!
How important is your testing?
Testing for issues is a critical part of developing any software, and it’s a meaningful way for anyone to contribute—whether or not you have experience. Details on what to test in WordPress 6.9 are here.
If you encounter an issue, please share it in the Alpha/Beta area of the support forums. If you are comfortable submitting a reproducible bugbugA bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. report, you can do so via WordPress Trac. You can also check your issue against this list of known bugs.
WordPress 6.9 will include many new features that were previously only available in the GutenbergGutenbergThe Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ plugin. Learn more about Gutenberg updates since WordPress 6.8 in the What’s New in Gutenberg posts for versions 20.4 & 20.5, 20.6 & 20.7,20.8 & 20.9,21,21.1,21.2, 21.3, 21.4, 21.5,21.6, 21.7, 21.8 & 21.9.
What’s new in WordPress 6.9?
This release brings major advancements in editing, collaboration, and developer capabilitiescapabilityA capability is permission to perform one or more types of task. Checking if a user has a capability is performed by the current_user_can function. Each user of a WordPress site might have some permissions but not others, depending on their role. For example, users who have the Author role usually have permission to edit their own posts (the “edit_posts” capability), but not permission to edit other users’ posts (the “edit_others_posts” capability)..
Site Editor
Expanded Template Management: Create multiple templates per slug, draft before publishing, activate or deactivate templates as needed, and retain custom templates when switching themes.
Content Creation & Editor Features
Notes: Notes can now be attached to individual blocks. This enables asynchronous collaboration and more efficient editorial workflows. This was formerly known as ‘BlockBlockBlock is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. Comments’.
Hide Blocks on Frontend: You can hide blocks from the frontend while leaving them editable in the backend—supporting staging, alternate design explorations, and non-destructive workflows.
New Blocks: Accordion, Terms Query, Math block and Time to Read. The ‘Fit text’ formatting option is now available for paragraph and heading blocks, providing more flexibility for site building.
Drag and drop block experience: Instead of dragging a copy, users now move the actual block itself within the editor while rearranging content. The result is a visually enhanced and accessible editing experience for all users
Command Palette
Command Palette (Press Ctrl+K or Command+K anywhere in the dashboard to use the command palette) is available across both the Editor and the Dashboard, making navigation and actions faster and easier. Simply type in the Command Palette to search, jump to specific screens, or trigger actions directly. This also lays the groundwork for future integrations with the new Abilities APIAPIAn API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways..
Developer & API Updates
New Abilities API: A unified registry of callable WordPress capabilities with defined inputs and outputs, built for AI integrations and developer automation.
Interactivity API Improvements: A new algorithm powers client-side navigation, enabling developers to build new user experiences that weren’t possible before and will be included in future WordPress versions, like instant search or client-side comment submissions.
DataViews & DataForm components: The release introduces support for more field types & new layouts. DataViews now offers infinite scroll for large datasets and allows for locked filters and improved multi-selection via the new DataViewsPicker.
HTMLHTMLHyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. API: These upgrades make parsing, transforming, and validating HTML safer and more efficient across blocks, site editor, and custom plugins, boosting programmatic HTML manipulation accuracy.
Block Binding API: Date block supports block bindings, image block allows binding the caption, an improved and extensibleExtensibleThis is the ability to add additional functionality to the code. Plugins extend the WordPress core software. user interface that allows custom sources in the bindings editor.
Performance
Introduced the “template enhancementenhancementEnhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. output buffer” to unlock new optimization opportunities.
Block styles loaded on demand in classic themes to reduce overall CSSCSSCascading Style Sheets. used.
Support for fetchpriority on scripts and script modules.
Support for printing script modules in the footer.
Increased inlining of stylesheets to reduce render blocking.
Minification of stylesheets in coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. block themes.
Scripts and styles for hidden blocks omitted by default.
Emoji detection script converted to a script module and moved to footer.
Database query optimizations and caching.
Cron spawned at shutdown instead of init to reduce impact on TTFB.
Improvements to RSS feedRSS FeedRSS is an acronym for Real Simple Syndication which is a type of web feed which allows users to access updates to online content in a standardized, computer-readable format. This is the feed. caching.
UTF-8 processing optimizations.
Additional Notes
No new default theme in 6.9: There is no bundled theme shipping with 6.9; the focus is on enhancing the editor experience, API support and performance.
Early Preview Plugins: MCP Adapter, and PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher AI Client are launching as canonical packages and plugins alongside 6.9, but are not part of Core.
The MCP Adaptor turns WordPress Abilities into MCP Tools that can be used by AI agents.
The PHP AI Client allows WordPress to connect to LLMS for AI powered content creation.
Just for you: a Beta 1 haiku
Beta moon arises, In its glow, we debug dreams— Stable stars ahead.
This post aims to prepare a calendar with the expected start time for each release party and who is involved in the upcoming 6.9 milestone.
The release party schedule will remain unchanged during the Release Candidaterelease candidateOne of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). phase and for the final release of WordPress 6.9. This allows contributors to attend and assist with release testing during the final weeks of the release cycle.
As always, there may be last-minute adjustments. The release squad will do its best to communicate any changes promptly.
Emcee / Release LeadRelease LeadThe community member ultimately responsible for the Release.
CommittercommitterA developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component.
BetaBetaA pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1
RCrelease candidateOne of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). 1
This post aims to prepare a calendar with the expected start time for each release party and who is involved in the upcoming 6.8 milestone.
The release party schedule will remain unchanged during the Release Candidaterelease candidateOne of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). phase and for the final release of WordPress 6.8. This is for practical reasons to allow additional contributors to attend and assist with release testing during the final weeks of the release cycle.
As has been seen in previous release cycles, things can change at the last minute, so expect some flexibility. The release squad will do its best to respect the calendar and communicate any changes promptly.
CommittercommitterA developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component.
BetaBetaA pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1
RCrelease candidateOne of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). 1
For the past several years, WordPress has been using a consistent set of titles for release squad members. Going forward the Release Coordinator role will become Release Coordination as the latter easier to translate reliably and neutrally in languages with gendered nouns.
The “… Lead” roles will remain unchanged.
This change is a result of a discussion on ticketticketCreated for both bug reports and feature development on the bug tracker.#62386 to explore adding missing release squad titles to WordPress CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress.. This will allow every release squad member to be celebrated accurately with their corresponding title on the credits page within the WordPress dashboard and through the WordPress.org Credits APIAPIAn API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways..
This post aims to prepare a calendar with the expected start time for each release party and who is involved in the upcoming 6.7 milestone.
The WordPress 6.7 release squad includes a significant number of contributors based in the APAC region. To account for this, release party times will be shifted during the WordPress 6.7 betaBetaA pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. period to be more APAC friendly.
The release party schedule will remain unchanged during the Release Candidaterelease candidateOne of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). phase and for the final release of WordPress 6.7. This is for practical reasons to allow additional contributors to attend and assist with release testing during the final weeks of the release cycle.
As has been seen in previous release cycles, things can change at the last minute, so expect some flexibility. The release squad will do its best to respect the calendar and communicate any changes promptly.
Date/Time
Milestone
Emcee
CommittercommitterA developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component.
RCrelease candidateOne of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). 1
Greetings from your friendly neighborhood 6.5 release coordinators—@priethor, @akshayar, and @marybaum! Below you will find the same calendar @francina built and used for 6.4, only updated with dates and other details for 6.5.
As we saw with several recent releases, things can change at the last minute. Still, the coordinators are starting to anticipate what could happen; work hard to respect the calendar—what is supposed to happen; and address what will happen in real time going forward, by letting you know of any change promptly.
If you can fill any of those roles, please add your name in the comments, with the date and role, so the three of us can finalize the calendar. It would be great to heave two people with the same access level for each party—then we can help each other if a party takes longer than expected.
Over the last three years or so, squads have aimed to start parties at 16:00 UTC because it does cover a range of time zones. We do have squad members in APAC, so it would be nice to start a little earlier — maybe 14:00 UTC, particularly once daylight time starts to kick in across the world.
For now, let’s think about 14:00 UTC and adjust as needed going forward.
Update February 13, 2024: The release party for BetaBetaA pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 2, on Tuesday, February 20, 2024, will start at 16:00 after a one-hour code freeze.
Please check the Hosting Release Page in the Handbook to read about the different roles.
Thank you for the team effort!
Date/Time
Milestone
Host
CommittercommitterA developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component.
Release Candidaterelease candidateOne of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). 1
This post aims to prepare a calendar with the expected start time for each release party and who is involved in the upcoming 6.4 milestones.
As we saw happening with 6.3 BetaBetaA pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1, things can change at the last minute, so expect some flexibility. The release team will do their best to respect the calendar and communicate any change promptly.
If you can fill any of those roles, please add your name in the comments, with the date and role, so that I can finalize the calendar. Having two people with the same access level for each party is also okay. This will allow us to help each other if the party takes longer than expected.
I always proposed 16:00 UTC for release parties because it’s a time that allows us to cover quite a few time zones. However, it does not favour contributors in APAC. I will contact those in that area to see if we have people with enough access to run at least one release party in their time zone.
Please check the Hosting Release Page in the Handbook to read about the different roles.
Thank you all for the team effort!
Date/Time
Milestone
Host
CommittercommitterA developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component.
Release Candidaterelease candidateOne of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). 1
This post aims to prepare a calendar with the expected start time for each release party and who is involved for the upcoming 6.3 milestones. Things can change at the last minute, as we saw happening with BetaBetaA pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1, so expect some flexibility around it. The release team will do their best to respect the calendar and communicate any change promptly. If you can fill any of those roles, please add your name in the comments, with the date and role, so I can finalize the calendar.
It’s ok also to have two people with the same access level for each party. This will allow us to help each other if the party takes longer than expected.
CommittercommitterA developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component.
Release Candidaterelease candidateOne of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). 1
