{"id":"src_oY9ynejq3UkKg9_TKurBu","slug":"wordpress-core-releases","name":"WordPress Core Releases","type":"feed","url":"https://wordpress.org/news/category/releases/","orgId":"org_NtIO3Mo7T-C0L5ZLZnIU_","org":{"slug":"wordpress","name":"WordPress"},"isPrimary":true,"metadata":"{\"feedUrl\":\"https://wordpress.org/news/category/releases/feed/\",\"feedType\":\"unknown\",\"feedDiscoveredAt\":\"2026-05-01T20:31:26.711Z\",\"noFeedFound\":false,\"feedLastModified\":\"Wed, 29 Apr 2026 13:14:55 GMT\"}","releaseCount":10,"releasesLast30Days":0,"avgReleasesPerWeek":0.8,"latestVersion":"7.0","latestDate":"2026-03-26T18:37:28.000Z","changelogUrl":null,"hasChangelogFile":false,"lastFetchedAt":"2026-05-01T20:31:49.424Z","lastPolledAt":"2026-05-01T21:01:07.391Z","trackingSince":"2026-02-03T18:07:31.000Z","releases":[{"id":"rel_UrqGQxELgH7yQGd3pkNvH","version":"7.0","title":"WordPress 7.0 Release Candidate 2","summary":"The second Release Candidate (“RC2”) for WordPress 7.0 is ready for download and testing!\n\n**This version of the WordPress software is under developme...","content":"The second Release Candidate (“RC2”) for WordPress 7.0 is ready for download and testing!\n\n**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 RC2 on a test server and site.\n\nReaching 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 7.0 is the best it can be.\n\nYou can test WordPress 7.0 RC2 in four ways:\n\n**Plugin**Install and activate the [WordPress Beta Tester](https://wordpress.org/plugins/wordpress-beta-tester/) plugin on a WordPress install. (Select the “Bleeding edge” channel and “Beta/RC Only” stream.)**Direct Download**Download the [RC2 version (zip)](https://wordpress.org/wordpress-7.0-RC2.zip) and install it on a WordPress website.**Command Line**Use this [WP-CLI](https://make.wordpress.org/cli/) command: \n`wp core update --version=7.0-RC2`**WordPress Playground**Use the [WordPress Playground instance](https://playground.wordpress.net/?php=8.0&wp=beta&networking=no&language=&multisite=no&random=y4q1rn88xn) to test the software directly in your browser.  No setup required – just click and go! \n\nThe scheduled final release date for WordPress 7.0 is **April 9, 2026**. The full [release schedule can be found here](https://make.wordpress.org/core/2026/02/12/wordpress-7-0-release-party-schedule/). 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!\n\nPlease continue checking the [Make WordPress Core blog](https://make.wordpress.org/core/) for [7.0-related posts](https://make.wordpress.org/core/tag/7-0) in the coming weeks for more information.\n\n## What’s in WordPress 7.0 RC2?\n\n**What’s new in WordPress 7.0**? Check out the [Beta 1 announcement](https://wordpress.org/news/2026/02/wordpress-7-0-beta-1/) and [7.0 Developer Notes](https://make.wordpress.org/core/tag/dev-notes+7-0/) for details and highlights. For technical information related to issues addressed since [RC1](https://wordpress.org/news/2026/03/wordpress-7-0-release-candidate-1/), you can browse the following links:\n\n- [GitHub commits](https://github.com/WordPress/gutenberg/commits/wp/7.0?since=2026-03-24&until=2026-03-26) since March 24, 2026\n\n- [Closed Trac tickets](https://core.trac.wordpress.org/query?status=closed&changetime=03%2F24%2F2026..03%2F26%2F2026&milestone=7.0&group=component&col=id&col=milestone&col=owner&col=type&col=priority&order=id) since March 24, 2026\n\n## How you can contribute\n\nWordPress is open source 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.\n\n## Get involved in testing\n\nTesting for issues is crucial to the development of any software. It’s also a meaningful way for anyone to contribute. \n\nYour help testing the WordPress 7.0 RC1 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](https://make.wordpress.org/test/2026/02/20/help-test-wordpress-7-0/) will walk you through testing features in WordPress 7.0. For those new to testing, follow [this general testing guide](https://make.wordpress.org/test/handbook/get-setup-for-testing/) for more details on getting set up.\n\nWhat else to test:\n\n- [Real Time Collaboration](https://make.wordpress.org/test/2026/03/11/its-time-to-test-real-time-collaboration/)\n\n- [Pattern Editing and content-only Interactivity](https://make.wordpress.org/test/2026/02/27/call-for-testing-pattern-editing-and-content-only-interactivity-in-wordpress-7-0/)\n\nIf you encounter an issue, please report it to the [Alpha/Beta area](https://wordpress.org/support/forum/alphabeta/) of the support forums or directly to [WordPress Trac](https://core.trac.wordpress.org/newticket) if you are comfortable writing a reproducible bug report.  You can also check your issue against a list of [known bugs](https://core.trac.wordpress.org/tickets/major). \n\nCurious about testing releases in general?  Follow along with the [testing initiatives in Make Core](https://make.wordpress.org/test/) and join the [#core-test channel](https://wordpress.slack.com/messages/core-test/) on [Making WordPress Slack](https://wordpress.slack.com/).\n\n### Test on your hosting platforms\n\nWeb 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.\n\nWant to test WordPress on your hosting system? [Get started with configuring distributed hosting tests here](https://make.wordpress.org/hosting/test-results-getting-started/).\n\n### Update your theme or plugin\n\nFor plugin and theme authors, your products play an integral role in extending the functionality and value of WordPress for all users.\n\nThanks for continuing to test your themes and plugins with the WordPress 7.0 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](https://developer.wordpress.org/plugins/wordpress-org/how-your-readme-txt-works/) to `7.0`.\n\nIf you find compatibility issues, please post detailed information to the [support forum](https://wordpress.org/support/forum/alphabeta/).\n\n## Help translate WordPress\n\nDo you speak a language other than English? ¿Español? Français? Русский? 日本語? हिन्दी? বাংলা? मराठी? ಕನ್ನಡ?  You can [help translate WordPress into more than 100 languages](https://translate.wordpress.org/projects/wp/dev/). This release milestone (RC2) also marks the [hard string freeze](https://make.wordpress.org/polyglots/handbook/glossary/#hard-freeze) point of the [7.0 release cycle](https://make.wordpress.org/core/2026/03/25/wordpress-7-0-release-candidate-phase/).\n\n## An RC2 haiku\n\n*At first just a dream*,\n\n*RC2 flows like a stream*\n\n*with seven-oh gleam.*\n\n*Props to [@amykamala](https://profiles.wordpress.org/amykamala/) *[@annezazu](https://profiles.wordpress.org/annezazu/) *for proofreading and review.*","publishedAt":"2026-03-26T18:37:28.000Z","url":"https://wordpress.org/news/2026/03/wordpress-7-0-release-candidate-2/","media":[]},{"id":"rel_tD7tbvFytk8_aBgZqT_od","version":"7.0","title":"WordPress 7.0 Release Candidate 1","summary":"The first Release Candidate (“RC1”) for WordPress 7.0 is ready for download and testing!\n\n**This version of the WordPress software is still under deve...","content":"The first Release Candidate (“RC1”) for WordPress 7.0 is ready for download and testing!\n\n**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 evaluate RC1 on a test server and site.\n\nWordPress 7.0 RC1 can be tested using any of the following methods:\n\n**Plugin**Install and activate the [WordPress Beta Tester](https://wordpress.org/plugins/wordpress-beta-tester/) plugin on a WordPress install. (Select the “Bleeding edge” channel and “Beta/RC Only” stream.)**Direct Download**Download the [RC1 version (zip)](https://wordpress.org/wordpress-7.0-RC1.zip) and install it on a WordPress website.**Command Line**Use this [WP-CLI](https://make.wordpress.org/cli/) command: \n`wp core update --version=7.0-`RC1**WordPress Playground**Use the [WordPress Playground instance](https://playground.wordpress.net/?php=8.0&wp=beta&networking=no&language=&multisite=no&random=y4q1rn88xn) to test the software directly in your browser.  No setup required – just click and go! \n\nThe scheduled final release date for WordPress 7.0 is **April 9, 2026**. The full [release schedule can be found here](https://make.wordpress.org/core/2026/02/12/wordpress-7-0-release-party-schedule/). 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!\n\nPlease continue checking the [Make WordPress Core blog](https://make.wordpress.org/core/) for [7.0-related posts](https://make.wordpress.org/core/tag/7-0) in the coming weeks for more information.\n\n## What’s in WordPress 7.0 RC1?\n\n**What’s new in WordPress 7.0**? Check out the [Beta 1 announcement](https://wordpress.org/news/2026/02/wordpress-7-0-beta-1/) and [WordPress 7.0 Developer Notes](https://make.wordpress.org/core/tag/dev-notes+7-0/) for details and highlights.\n\nRC1 contains more than 134 updates and fixes since the Beta 5 release. You can browse the technical details for all issues addressed since Beta 5 using these links:\n\n- [GitHub commits](https://github.com/WordPress/gutenberg/commits/wp/7.0?since=2026-03-12&until=2026-03-24) since March 12, 2026\n\n- [Closed Trac tickets](https://core.trac.wordpress.org/query?status=closed&changetime=03%2F12%2F2026..03%2F24%2F2026&milestone=7.0&group=component&col=id&col=summary&col=owner&col=type&col=priority&order=id) since March 12, 2026\n\n### New Features since Beta 1\n\nThe release squad in conjunction with project leadership identified additional features that were not ready for beta 1 but are included in RC1 as supporting requirements for flagship features of the release.\n\n- [AI Connectors Screen](https://core.trac.wordpress.org/ticket/64730) – A new admin screen for connecting AI providers to your site and an [API for registering additional ones](https://core.trac.wordpress.org/ticket/64791).\n\n- [The Command Palette](https://github.com/WordPress/gutenberg/pull/75757) is now available via a `⌘K` or `Ctrl+K` shortcut in the admin bar.\n\nWant to look deeper into the details and technical notes for this release? These tickets and pull requests are just some of the latest updates:\n\n- [#GB-76700](https://github.com/WordPress/gutenberg/pull/76700): Client Side Media as plugin only\n\n- [#GB-76722](https://github.com/WordPress/gutenberg/pull/76722): Add support for non-AI providers on Connector’s Screen\n\n- [#GB-76736](https://github.com/WordPress/gutenberg/pull/76736): New activation hook to enable RTC by default\n\n- [#64904](https://core.trac.wordpress.org/ticket/64904): `WP_ALLOW_COLLABORATION` constant for RTC\n\n- [#](https://github.com/WordPress/gutenberg/pull/76704)[GB-76704](https://github.com/WordPress/gutenberg/pull/76643): Increased polling intervals for RTC\n\n- [#GB-76643](https://github.com/WordPress/gutenberg/pull/76643): Real Time Collaboration is opt-in by default\n\n- [#GB-76460](https://github.com/WordPress/gutenberg/pull/76460): Toggle to turn RTC session notifications on/off\n\n- [#62046](https://core.trac.wordpress.org/changeset/62046): Update PHP AI Client package to 1.3.1\n\n- [#GB-76550](https://github.com/WordPress/gutenberg/pull/76550): Revisions: Show changed block attributes in sidebar\n\n- [#62067](https://core.trac.wordpress.org/changeset/62067): Single config option to disable all LLM related features\n\n- [#63697](https://core.trac.wordpress.org/ticket/63697): OPCache added to `Site Health > Info > Server`\n\n**The final release is on track for April 9, 2026.** As always, a successful release depends on your confirmation during testing. So please download and test!\n\n## How you can contribute\n\nWordPress is open source 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.\n\n### Help test this release\n\nTesting 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 7.0 RC1 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](https://make.wordpress.org/test/2026/02/20/help-test-wordpress-7-0/) will walk you through testing features in WordPress 7.0.\n\nWhat to test:\n\n- [Real Time Collaboration](https://make.wordpress.org/test/2026/03/11/its-time-to-test-real-time-collaboration/)\n\n- [Pattern Editing and content-only Interactivity](https://make.wordpress.org/test/2026/02/27/call-for-testing-pattern-editing-and-content-only-interactivity-in-wordpress-7-0/)\n\nIf you encounter an issue, please report it to the [Alpha/Beta area](https://wordpress.org/support/forum/alphabeta/) of the support forums or directly to [Trac](https://core.trac.wordpress.org/newticket) if you are comfortable writing a reproducible bug report. You can also check your issue against a list of [known bugs](https://core.trac.wordpress.org/tickets/major).\n\n### Test on your hosting platforms\n\nHosting systems provide vital infrastructure for supporting WordPress and its users. Testing on hosting infrastructure ensures that WordPress and hosting systems are fully compatible, free of errors, optimized for the best possible user experience, and that updates roll out to customer sites without issue. Thank you to all [web hosts who test WordPress](https://make.wordpress.org/hosting/test-results/)!\n\nWant to set up testing on your hosting system? [Get started with configuring distributed hosting tests here](https://make.wordpress.org/hosting/test-results-getting-started/).\n\n### Update your theme or plugin\n\nFor plugin and theme authors, your products play an integral role in extending the functionality and value of WordPress for all users.\n\nThanks for continuing to test your themes and plugins with the WordPress 7.0 beta releases. With RC1, you’ll want to conclude your testing and update the *“Tested up to”* version in your [plugin’s readme file](https://developer.wordpress.org/plugins/wordpress-org/how-your-readme-txt-works/) to `7.0`. If you find compatibility issues, please post detailed information to the [support forum](https://wordpress.org/support/forum/alphabeta/).\n\nCurious about testing releases in general? Follow along with the [testing initiatives](https://make.wordpress.org/test/) and join the [#core-test channel](https://wordpress.slack.com/messages/core-test/) on [Making WordPress Slack](https://wordpress.slack.com/).\n\n## Help translate WordPress\n\nDo you speak a language other than English? ¿Español? Français? Русский? 日本語? हिन्दी? বাংলা? मराठी? ಕನ್ನಡ?  You can [help translate WordPress into more than 100 languages](https://make.wordpress.org/polyglots/handbook/translating/). This release milestone (RC1) marks the [hard string freeze](https://make.wordpress.org/polyglots/handbook/glossary/#hard-freeze) point of the 7.0 release cycle. However, strings will not be available for translation until RC2 later this week.\n\n## An RC1 haiku\n\n*RC1 arrives*\n\n*with momentum, sped up time*\n\n*and jazz on the mind.*\n\n*Props to [@4thhubbard](https://profiles.wordpress.org/4thhubbard/), [@desrosj](https://profiles.wordpress.org/desrosj/), [@jeffpaul](https://profiles.wordpress.org/jeffpaul/), [@chaion07](https://profiles.wordpress.org/chaion07/), [@audrasjb](https://profiles.wordpress.org/audrasjb/), [@jorbin](https://profiles.wordpress.org/jorbin/) for collaboration and review.*","publishedAt":"2026-03-24T19:32:15.000Z","url":"https://wordpress.org/news/2026/03/wordpress-7-0-release-candidate-1/","media":[]},{"id":"rel_Q2NkAWeJZyoHOEzT5xU7p","version":"7.0","title":"WordPress 7.0 Beta 5","summary":"WordPress 7.0 Beta 5 is ready for download and testing!\n\n**This version of the WordPress software is still under development**. Please do not install,...","content":"WordPress 7.0 Beta 5 is ready for download and testing!\n\n**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 5 on a test server and site.WordPress 7.0 Beta 5 can be tested using any of the following methods:\n\n**Plugin**Install and activate the [WordPress Beta Tester](https://wordpress.org/plugins/wordpress-beta-tester/) plugin on a WordPress install. (Select the “Bleeding edge” channel and “Beta/RC Only” stream.)**Direct Download**Download the [Beta 5 version (zip)](https://wordpress.org/wordpress-7.0-beta5.zip) and install it on a WordPress website.**Command Line**Use this [WP-CLI](https://make.wordpress.org/cli/) command:\n`wp core update --version=7.0-beta`5**WordPress Playground**Use the [WordPress Playground instance](https://playground.wordpress.net/?php=8.0&wp=beta&networking=no&language=&multisite=no&random=y4q1rn88xn) to test the software directly in your browser.  No setup is required – just click and go! \n\nThe scheduled final release date for WordPress 7.0 is still **April 9, 2026**.  The full [release schedule can be found here](https://make.wordpress.org/core/2026/02/12/wordpress-7-0-release-party-schedule/). 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!\n\nPlease continue checking the [Make WordPress Core blog](https://make.wordpress.org/core/) for [7.0-related posts](https://make.wordpress.org/core/tag/7-0) in the coming weeks for more information. **What’s new in WordPress 7.0**? Check out the [Beta 1](https://wordpress.org/news/2026/02/wordpress-7-0-beta-1/), [Beta 2](https://wordpress.org/news/2026/02/wordpress-7-0-beta-2/), [Beta 3](https://wordpress.org/news/2026/03/wordpress-7-0-beta-3/) and [Beta 4](https://wordpress.org/news/2026/03/wordpress-6-9-3-and-7-0-beta-4/) announcements for details and highlights.\n\n## How to test this release\n\nYour help testing the WordPress 7.0 Beta 5 version is key to ensuring everything in the release is the best it can be. While testing the upgrade process is essential, trying out new features is equally important. This [detailed guide](https://make.wordpress.org/test/2026/02/20/help-test-wordpress-7-0/) will walk you through testing features in WordPress 7.0.\n\nIf you encounter an issue, please report it to the [Alpha/Beta area](https://wordpress.org/support/forum/alphabeta/) of the support forums or directly to [WordPress Trac](https://core.trac.wordpress.org/newticket) if you are comfortable writing a reproducible bug report. You can also check your issue against a list of [known bugs](https://core.trac.wordpress.org/tickets/major).Curious about testing releases in general? Follow along with the [testing initiatives in Make Core](https://make.wordpress.org/test/) and join the [#core-test channel](https://wordpress.slack.com/messages/core-test/) on [Making WordPress Slack](https://wordpress.slack.com/).\n\n## Beta 5 updates and highlights\n\nWordPress 7.0 Beta 5 contains more than 101 updates and fixes since the Beta 3 release.\n\nEach beta cycle focuses on bug fixes, and more are on the way with your help through testing. You can browse the technical details for all issues addressed since Beta 3 using these links:\n\n- [GitHub commits](https://github.com/WordPress/gutenberg/commits/wp/7.0?since=2026-03-05&until=2026-03-12) since March 5, 2026\n\n- [Closed Trac tickets](https://core.trac.wordpress.org/query?status=closed&changetime=03%2F05%2F2026..03%2F12%2F2026&milestone=7.0&group=component&col=id&col=milestone&col=owner&col=type&col=priority&order=id) since March 5, 2026\n\nIssues addressed since Beta 4:\n\n- [GitHub commits](https://github.com/WordPress/gutenberg/commits/wp/7.0?since=2026-03-10&until=2026-03-12) since March 10, 2026\n\n- [Closed Trac tickets](https://core.trac.wordpress.org/query?status=closed&changetime=03%2F10%2F2026..03%2F12%2F2026&milestone=7.0&group=component&col=id&col=milestone&col=owner&col=type&col=priority&order=id) since March 10, 2026\n\n**WordPress 7.0 Beta 5 contains a new feature!**\n\nInstantly access all the tools you need with a single click using the **new Command Palette shortcut in the Omnibar**! In 7.0 Beta 5, logged-in editors will see a field with a `⌘K` or `Ctrl+K` symbol in the upper admin bar that unfurls the command palette when clicked. The new command palette entry point streamlines navigation and customization, giving you full control from anywhere on your site – whether you’re editing, designing or just browsing plugins.\n\n## A Beta 5 haiku\n\n*A smooth melody*\n\n*Beta 5 plays on its strings.*\n\n*Seven brings good things.*\n\n*Props to [@amykamala](https://profiles.wordpress.org/amykamala/), [@annezazu](https://profiles.wordpress.org/annezazu/) and [@4thhubbard](https://profiles.wordpress.org/4thhubbard/) for proofreading and review.*","publishedAt":"2026-03-12T15:49:14.000Z","url":"https://wordpress.org/news/2026/03/wordpress-7-0-beta-5/","media":[]},{"id":"rel_4ObeH-yMotPGtlHx4PJkT","version":"6.9.4","title":"WordPress 6.9.4 Release","summary":"## WordPress 6.9.4 is now available\n\n[WordPress 6.9.2](https://wordpress.org/news/2026/03/wordpress-6-9-2-release/) and [WordPress 6.9.3](https://word...","content":"## WordPress 6.9.4 is now available\n\n[WordPress 6.9.2](https://wordpress.org/news/2026/03/wordpress-6-9-2-release/) and [WordPress 6.9.3](https://wordpress.org/news/2026/03/wordpress-6-9-3-and-7-0-beta-4/) were released yesterday, addressing 10 security issues and a bug that affected template file loading on a limited number of sites.\n\nThe WordPress Security Team has discovered that not all of the security fixes were fully applied, therefore 6.9.4 has been released containing the necessary additional fixes.\n\nBecause this is a security release,** it is recommended that you update your sites immediately**.\n\nYou can [download WordPress 6.9.4 from WordPress.org](https://wordpress.org/wordpress-6.9.4.zip), or visit your WordPress Dashboard, click “Updates”, and then click “Update Now”. If you have sites that support automatic background updates, the update process will begin automatically.\n\nFor more information on WordPress 6.9.4, please visit the [version page on the HelpHub site](https://wordpress.org/documentation/wordpress-version/version-6-9-4/).\n\n## Security updates included in this release\n\nThe security team would like to thank the contributors who reported and investigated this issue, in particular [Thomas Kräftner](https://profiles.wordpress.org/kraftner) for his responsible disclosure. The security issues that are resolved in 6.9.4 are:\n\n- A PclZip path traversal issue reported independently by [Francesco Carlucci](https://profiles.wordpress.org/francescocarlucci/) and [kaminuma](https://profiles.wordpress.org/kaminuma/)\n\n- An authorization bypass on the Notes feature reported by [kaminuma](https://profiles.wordpress.org/kaminuma/)\n\n- An XXE in the external getID3 library reported by [Youssef Achtatal](https://profiles.wordpress.org/regex33/)","publishedAt":"2026-03-11T15:34:58.000Z","url":"https://wordpress.org/news/2026/03/wordpress-6-9-4-release/","media":[]},{"id":"rel_82vjUuxpB6YvCXZhPkuKj","version":"6.9.3","title":"WordPress 6.9.3 and 7.0 beta 4","summary":"[WordPress 6.9.2 was released earlier today](https://wordpress.org/news/2026/03/wordpress-6-9-2-release/) and addressed 10 security issues.\n\nA few use...","content":"[WordPress 6.9.2 was released earlier today](https://wordpress.org/news/2026/03/wordpress-6-9-2-release/) and addressed 10 security issues.\n\nA few users have subsequently reported an issue where the front end of their site was appearing blank after updating to 6.9.2. The issue has been narrowed down to some themes using an unusual approach to loading template files via “stringable objects” instead of primitive strings for file paths.\n\nAlthough this is is not an officially supported approach to loading template files in WordPress (the `template_include` filter only accepts a string), it nevertheless caused some sites to break. As a result, the Security Team has decided to address this in a fast follow 6.9.3 release.\n\nAs always,** it is recommended that you update your sites to the latest version of WordPress immediately.** This ensures your site is protected by all available security fixes in 6.9.2 and that you will not be affected by the bug fixed in 6.9.3.\n\nMany thanks to those who reported the issue, assisted in narrowing down the problem, and helped with the fix, in particular [Jos Klever](https://profiles.wordpress.org/josklever/) who assisted throughout the process.\n\nYou can [download WordPress 6.9.3 from WordPress.org](https://wordpress.org/wordpress-6.9.3.zip), or visit your WordPress Dashboard, click “Updates”, and then click “Update Now”. If you have sites that support automatic background updates, the update process will begin shortly. You don’t have to do a thing!\n\nFor more information on WordPress 6.9.3, please visit the [version page on the HelpHub site](https://wordpress.org/documentation/wordpress-version/version-6-9-3/).\n\n## WordPress 7.0 beta 4\n\nThe next major release of WordPress will be [version 7.0](https://make.wordpress.org/core/7-0/), which is planned for April 9, 2026. The Security Team has decided to package a new beta release (7.0 beta 4) to keep everyone protected from the patched vulnerabilities, including the dedicated members of the community focusing their time and effort on testing the upcoming release.\n\n**This will be an additional beta release in the 7.0 release cycle.** The schedule will remain the same going forward, but with five total beta releases instead of the previously planned four. The next 7.0 beta release is still scheduled for Thursday, March 12th.\n\n**This beta version of the WordPress software is still under development**. Please do not install, run, or test WordPress 7.0 beta versions on production or mission-critical websites. Instead, you should evaluate Beta 4 on a test server and site.\n\n**Plugin**Install and activate the [WordPress Beta Tester](https://wordpress.org/plugins/wordpress-beta-tester/) plugin on a WordPress install. (Select the “Bleeding edge” channel and “Beta/RC Only” stream.)**Direct Download**Download the [Beta 4 version (zip)](https://wordpress.org/wordpress-7.0-beta4.zip) and install it on a WordPress website.**Command Line**Use this [WP-CLI](https://make.wordpress.org/cli/) command: \n`wp core update --version=7.0-beta`4**WordPress Playground**Use the [WordPress Playground instance](https://playground.wordpress.net/?php=8.0&wp=beta&networking=no&language=&multisite=no&random=y4q1rn88xn) to test the software directly in your browser.  No setup is required – just click and go! \n\n## Beta 4 updates and highlights\n\nWordPress 7.0 Beta 4 contains the ten security patches shipped in WordPress 6.9.2, and more than 49 updates and fixes since the Beta 3 release, including 14 in the Editor and 35 in Core. \n\nEach beta cycle focuses on bug fixes. More are on the way, thanks to your help with testing. You can browse the technical details for all issues addressed since Beta 3 at these links:\n\n- [GitHub commits for 7.0 ](https://github.com/WordPress/gutenberg/compare/f4d8a5803aa2fbe26e7d9af4d17e80a622b7bab8...9b8144036fa5faf75de43d4502ff9809fcf689ad) since March 5, 2026\n\n- [Closed Trac tickets for 7.0](https://core.trac.wordpress.org/query?status=closed&changetime=03%2F05%2F2026..03%2F10%2F2026&milestone=7.0&group=component&col=id&col=summary&col=milestone&col=owner&col=type&col=priority&order=id) since March 5, 2026\n\nAs always, a successful release depends on your confirmation during testing. So please download and test!\n\n*Props [@peterwilson](https://profiles.wordpress.org/peterwilson/), [@desrosj](https://profiles.wordpress.org/desrosj/), [@marybaum](https://profiles.wordpress.org/marybaum/), [@amykamala](https://profiles.wordpress.org/amykamala/) for peer reviewing.*","publishedAt":"2026-03-10T23:41:33.000Z","url":"https://wordpress.org/news/2026/03/wordpress-6-9-3-and-7-0-beta-4/","media":[]},{"id":"rel_XvtVZY1eQTBYL1qcXHkRM","version":"6.9.2","title":"WordPress 6.9.2 Release","summary":"## WordPress 6.9.2 is now available\n\nThis is a security release that features several fixes.\n\nBecause this is a security release,** it is recommended ...","content":"## WordPress 6.9.2 is now available\n\nThis is a security release that features several fixes.\n\nBecause this is a security release,** it is recommended that you update your sites immediately**.\n\nYou can [download WordPress 6.9.2 from WordPress.org](https://wordpress.org/wordpress-6.9.2.zip), or visit your WordPress Dashboard, click “Updates”, and then click “Update Now”. If you have sites that support automatic background updates, the update process will begin automatically.\n\nFor more information on WordPress 6.9.2, please visit the [version page on the HelpHub site](https://wordpress.org/documentation/wordpress-version/version-6-9-2/).\n\n## Security updates included in this release\n\nThe security team would like to thank the following people for [responsibly reporting vulnerabilities](https://hackerone.com/wordpress?type=team), and allowing them to be fixed in this release:\n\n- A Blind SSRF issue reported by [sibwtf](https://hackerone.com/sibwtf), and subsequently by several other researchers while the fix was being worked on\n\n- A PoP-chain weakness in the HTML API and Block Registry reported by [Phat RiO](https://github.com/hackerlo2003)\n\n- A regex DoS weakness in numeric character references reported by Dennis Snell of the WordPress Security Team\n\n- A stored XSS in nav menus reported by [Phill Savage](https://x.com/Savphill)\n\n- An AJAX `query-attachments` authorization bypass reported by [Vitaly Simonovich](https://www.vitalysim.com/)\n\n- A stored XSS via the `data-wp-bind` directive reported by [kaminuma](https://profiles.wordpress.org/kaminuma/)\n\n- An XSS that allows overridding client-side templates in the admin area reported by [Asaf Mozes](https://hackerone.com/amosec)\n\n- A PclZip path traversal issue reported independently by [Francesco Carlucci](https://profiles.wordpress.org/francescocarlucci/) and [kaminuma](https://profiles.wordpress.org/kaminuma/)\n\n- An authorization bypass on the Notes feature reported by [kaminuma](https://profiles.wordpress.org/kaminuma/)\n\n- An XXE in the external getID3 library reported by [Youssef Achtatal](https://profiles.wordpress.org/regex33/)\n\nThe WordPress security team have worked with the maintainer of the external getID3 library, James Heinrich, to coordinate a fix to getID3. A new version of getID3 [is available here](https://github.com/JamesHeinrich/getID3/releases).\n\nAs a courtesy, these fixes are being backported, where necessary, to all branches eligible to receive security fixes (currently through 4.7). As a reminder, **only the most recent version of WordPress is actively supported**. The backports are in progress and will ship as they become ready.\n\n## Thank you to these WordPress contributors\n\nThis release was led by [John Blackbourn](https://profiles.wordpress.org/johnbillion/). In addition to the security researchers mentioned above, WordPress 6.9.2 would not have been possible without the contributions of the following people: [Dennis Snell](https://profiles.wordpress.org/dmsnell/), [Alex Concha](https://profiles.wordpress.org/xknown/), [Jon Surrell](https://profiles.wordpress.org/jonsurrell/), [Isabel Brison](https://profiles.wordpress.org/isabel_brison/), [Peter Wilson](https://profiles.wordpress.org/peterwilsoncc/), [Jonathan Desrosiers](https://profiles.wordpress.org/desrosj/), [Jb Audras](https://profiles.wordpress.org/audrasjb/), [Luis Herranz](https://profiles.wordpress.org/luisherranz/), [Aaron Jorbin](https://profiles.wordpress.org/jorbin/), [Weston Ruter](https://profiles.wordpress.org/westonruter/), and [Dominik Schilling](https://profiles.wordpress.org/ocean90/).","publishedAt":"2026-03-10T15:43:19.000Z","url":"https://wordpress.org/news/2026/03/wordpress-6-9-2-release/","media":[]},{"id":"rel_0CVKnjHfKsLkFEA9AFDux","version":"7.0","title":"WordPress 7.0 Beta 3","summary":"WordPress 7.0 Beta 3 is available for download and testing!\n\n**This beta version of the WordPress software is still under development**. Please do not...","content":"WordPress 7.0 Beta 3 is available for download and testing!\n\n**This beta 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, you should evaluate Beta 3 on a test server and site.WordPress 7.0 Beta 3 can be tested using any of the following methods:\n\n**Plugin**Install and activate the [WordPress Beta Tester](https://wordpress.org/plugins/wordpress-beta-tester/) plugin on a WordPress install. (Select the “Bleeding edge” channel and “Beta/RC Only” stream.)**Direct Download**Download the [Beta 3 version (zip)](https://wordpress.org/wordpress-7.0-beta3.zip) and install it on a WordPress website.**Command Line**Use this [WP-CLI](https://make.wordpress.org/cli/) command: \n`wp core update --version=7.0-beta`3**WordPress Playground**Use the [WordPress Playground instance](https://playground.wordpress.net/?php=8.0&wp=beta&networking=no&language=&multisite=no&random=y4q1rn88xn) to test the software directly in your browser.  No setup is required – just click and go! \n\nThe scheduled final release date for WordPress 7.0 is **April 9, 2026**.  The full [release schedule can be found here](https://make.wordpress.org/core/2026/02/12/wordpress-7-0-release-party-schedule/). Your help testing Beta and RC versions is vital to making this release as stable and powerful as possible. Please continue checking the [Make WordPress Core blog](https://make.wordpress.org/core/) for [7.0-related posts](https://make.wordpress.org/core/tag/7-0) in the coming weeks for more information. Thank you to everyone who is contributing with testing!\n\n**Catch up on what’s new in WordPress 7.0**: Read the [Beta 2 announcement](https://wordpress.org/news/2026/02/wordpress-7-0-beta-2/) for details and highlights.\n\n## How to test this release\n\nYour help testing the WordPress 7.0 Beta 3 version is key to ensuring everything in the release is the best it can be. While testing the upgrade process is essential, trying out new features is equally important. This [detailed guide](https://make.wordpress.org/test/2026/02/20/help-test-wordpress-7-0/) will walk you through testing features in WordPress 7.0.\n\nIf you encounter an issue, please report it to the [Alpha/Beta area](https://wordpress.org/support/forum/alphabeta/) of the support forums or directly to [WordPress Trac](https://core.trac.wordpress.org/newticket) if you are comfortable writing a reproducible bug report. You can also check your issue against a list of [known bugs](https://core.trac.wordpress.org/tickets/major).Curious about testing releases in general? Follow along with the [testing initiatives in Make Core](https://make.wordpress.org/test/) and join the [#core-test channel](https://wordpress.slack.com/messages/core-test/) on [Making WordPress Slack](https://wordpress.slack.com/).\n\n## Beta 3 updates and highlights\n\nWordPress 7.0 Beta 3 contains more than 148 updates and fixes since the Beta 2 release, including 70 in the Editor and 78 in Core. \n\nEach beta cycle focuses on bug fixes, and more are on the way with your help through testing. You can browse the technical details for all issues addressed since Beta 2 using these links:\n\n- [GitHub commits for 7.0 ](https://github.com/WordPress/gutenberg/commits/wp/7.0?since=2026-02-26&until=2026-03-05) since February 26, 2026\n\n- [Closed Trac tickets for 7.0](https://core.trac.wordpress.org/query?status=closed&changetime=02%2F26%2F2026..03%2F05%2F2026&milestone=7.0&col=id&col=milestone&col=owner&col=type&col=priority&order=id) since February 26, 2026\n\nTapping into the power of AI is even easier in Beta 3! The WP AI Client Connectors screen now dynamically registers providers from the WP AI Client registry, in addition to the 3 default providers, giving users more flexibility and command over AI integrations.\n\n## A Beta 3 haiku\n\n*Through sun set and rise,*\n\n*Beta 3 takes off and flies.*\n\n*Seven soon arrives.*\n\n*Props to [@annezazu](https://profiles.wordpress.org/annezazu/)*, *[@jeffpaul](https://profiles.wordpress.org/jeffpaul/)*, *[@chaion07](https://profiles.wordpress.org/chaion07/)*,* [@audrasjb](https://profiles.wordpress.org/audrasjb/) and [@valentingrenier](https://profiles.wordpress.org/valentingrenier/) for proofreading and review.*","publishedAt":"2026-03-05T14:47:00.000Z","url":"https://wordpress.org/news/2026/03/wordpress-7-0-beta-3/","media":[]},{"id":"rel_PeFizVVKoa_7eeH9Yv0ny","version":"7.0","title":"WordPress 7.0 Beta 2","summary":"WordPress 7.0 Beta 2 is now ready for testing!\n\n**This beta version of the WordPress software is under development**. Please do not install, run, or t...","content":"WordPress 7.0 Beta 2 is now ready for testing!\n\n**This beta 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, you should evaluate Beta 2 on a test server and site. You can test WordPress 7.0 Beta 2 in any of the following ways:\n\n**Plugin**Install and activate the [WordPress Beta Tester](https://wordpress.org/plugins/wordpress-beta-tester/) plugin on a WordPress install. (Select the “Bleeding edge” channel and “Beta/RC Only” stream.)**Direct Download**Download the [Beta 2 version (zip)](https://wordpress.org/wordpress-7.0-beta2.zip) and install it on a WordPress website.**Command Line**Use this [WP-CLI](https://make.wordpress.org/cli/) command: \n`wp core update --version=7.0-beta2`**WordPress Playground**Use the [WordPress Playground instance](https://playground.wordpress.net/?php=8.0&wp=beta&networking=no&language=&multisite=no&random=y4q1rn88xn) to test the software directly in your browser.  No setup required – just click and go! \n\nThe scheduled final release date for WordPress 7.0 is **April 9, 2026**. The full [release schedule can be found here](https://make.wordpress.org/core/2026/02/12/wordpress-7-0-release-party-schedule/). Your help testing Beta and RC versions is vital to making this release as stable and powerful as possible. Make sure to check the [Make WordPress Core blog](https://make.wordpress.org/core/) for [7.0-related posts](https://make.wordpress.org/core/tag/7-0) in the coming weeks for more information. Thank you to everyone who contributes by testing!\n\n**Catch up on what’s new in WordPress 7.0**: Read the [Beta 1 announcement](https://wordpress.org/news/2026/02/wordpress-7-0-beta-1/) for details and highlights.\n\n## How to test this release\n\nYour help testing WordPress 7.0 Beta 2 is key to ensuring everything in the release is the best it can be. While testing the upgrade process is essential, trying out new features is equally important. This [guide on what to test in WordPress 7.0](https://make.wordpress.org/test/2026/02/20/help-test-wordpress-7-0/) will walk you through testing features in WordPress 7.0.\n\nIf you encounter an issue, please report it to the [Alpha/Beta area](https://wordpress.org/support/forum/alphabeta/) of the support forums or directly to [WordPress Trac](https://core.trac.wordpress.org/newticket) if you are comfortable writing a reproducible bug report. You can also check your issue against a list of [known bugs](https://core.trac.wordpress.org/tickets/major). Curious about testing releases in general? Follow along with the [testing initiatives in Make Core](https://make.wordpress.org/test/) and join the [#core-test channel](https://wordpress.slack.com/messages/core-test/) on [Making WordPress Slack](https://wordpress.slack.com/).\n\n## Beta 2 updates and highlights\n\nWordPress 7.0 Beta 2 contains more than 70 updates and fixes across the Editor and Core since the Beta 1 release. \n\nEach beta cycle focuses on bug fixes; and more are on the way with your help through testing. You can browse the technical details for all issues addressed since Beta 1 using these links:\n\n- [GitHub commits for 7.0](https://github.com/WordPress/gutenberg/commits/wp/7.0?since=2026-02-20&until=2026-02-26) since February 20, 2026\n\n- [Closed Trac tickets for 7.0](https://core.trac.wordpress.org/query?status=closed&changetime=02%2F20%2F2026..02%2F26%2F2026&milestone=7.0&col=id&col=milestone&col=owner&col=type&col=priority&order=id) since February 20, 2026\n\n**Beta 2 also contains a new feature**!\n\nAI provider management is more intuitive in 7.0 Beta 2 with a new Connectors UI dashboard page. WordPress users can now manage external AI connections in a central place in wp-admin, under Settings > Connectors. The new UI enables users to add, delete, and update external connections. It is powered by an extensible, route-based architecture that allows plugins and themes to hook into the page and expand its functionality. The new Connectors page builds on PHP-based script and menu infrastructure, and adds route components powered by `@wordpress/components` and `@wordpress/admin-ui`. A new `connections-wp-admin-init` hook and registration APIs allow plugins to integrate cleanly. This makes managing external connections easier while giving developers a clearer path to extend the experience.\n\n## A Beta 2 haiku\n\n*New, and fresh as dew*\n\n*Crafted and refined for you:*\n\n*Beta 2 breaks through.*\n\n*Props to [@4thhubbard](https://profiles.wordpress.org/4thhubbard/), [@annezazu](https://profiles.wordpress.org/annezazu/)*, *[@audrasjb](https://profiles.wordpress.org/audrasjb/), [@mukesh27](https://profiles.wordpress.org/mukesh27/), and [@chaion07](https://profiles.wordpress.org/chaion07/)* *for collaboration, proofreading and review.*","publishedAt":"2026-02-26T16:32:56.000Z","url":"https://wordpress.org/news/2026/02/wordpress-7-0-beta-2/","media":[]},{"id":"rel_dlzZAxiHi_5fs6SgukMLx","version":"7.0","title":"WordPress 7.0 Beta 1","summary":"WordPress 7.0 Beta 1 is ready for download and testing! **This beta release is intended for testing and development** only. Please do not install, run...","content":"WordPress 7.0 Beta 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.\n\n## How to Test WordPress 7.0 Beta 1\n\nYou can test WordPress 7.0 Beta 1 in any of the following ways:\n\n**Plugin**Install and activate the [WordPress Beta Tester](https://wordpress.org/plugins/wordpress-beta-tester/) plugin on a WordPress install. (Select the “Bleeding edge” channel and “Beta/RC Only” stream.)**Direct Download**Download the [Beta 1 version (zip)](https://wordpress.org/wordpress-7.0-beta1.zip) and install it on a WordPress website.**Command Line**Use this [WP-CLI](https://make.wordpress.org/cli/) command: `wp core update --version=7.0-beta1`**WordPress Playground**Use a [7.0 Beta 1 WordPress Playground instance](https://playground.wordpress.net/?php=8.3&wp=beta&networking=no&language=&multisite=no&random=r8nny4q18x) to test the software directly in your browser. No setup required – just click and go!\n\nThe scheduled final release date for WordPress 7.0 is **April 9, 2026**. The full [release schedule can be found here](https://make.wordpress.org/core/2026/02/12/wordpress-7-0-release-party-schedule/). 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!\n\n## How important is your testing?\n\nTesting 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 7.0 are available here](https://make.wordpress.org/test/2026/02/20/help-test-wordpress-7-0/).\n\nIf you encounter an issue, please share it in the [Alpha/Beta area](https://wordpress.org/support/forum/alphabeta/) of the support forums. If you are comfortable submitting a reproducible bug report, you can do so [via WordPress Trac](https://core.trac.wordpress.org/newticket). You can also check your issue against this list of [known bugs](https://core.trac.wordpress.org/tickets/major).\n\nCurious about testing releases in general and how to get started? Follow along with the [testing initiatives in Make Core](https://make.wordpress.org/test/) and join the [#core-test channel](https://wordpress.slack.com/messages/core-test/) on [Making WordPress Slack](https://wordpress.slack.com/). WordPress 7.0 will include new features that were previously only available in the Gutenberg plugin. Learn more about Gutenberg updates since WordPress 6.9 in the [What’s New in Gutenberg](https://make.wordpress.org/core/tag/gutenberg-new/) posts for versions [22.0](https://make.wordpress.org/core/2025/11/05/whats-new-in-gutenberg-22-0-05-november/), [22.1](https://make.wordpress.org/core/2025/11/20/whats-new-in-gutenberg-22-1-18-november-2025/), [22.2](https://make.wordpress.org/core/2025/12/03/whats-new-in-gutenberg-22-2-dec3/), [22.3](https://make.wordpress.org/core/2025/12/17/gutenberg-22-3-december-17/), [22.4](https://make.wordpress.org/core/2026/01/22/whats-new-in-gutenberg-22-4-20-january/), [22.5](https://make.wordpress.org/core/2026/02/04/whats-new-in-gutenberg-22-5-04-february/) & 22.6.\n\n## What’s new in WordPress 7.0?\n\nWordPress 7.0 boasts numerous upgrades in the editing and admin experience, delivering enhanced real time collaboration, refined customizability, new dashboard styles, and an expanded developer toolbox for people who create, design, and build with WordPress every day.\n\nWorking as a team just got easier with the ability for multiple users to edit together in real time, while visual revisions allow a visual comparison between page versions, adding agility to the creation and review process. Working with patterns has been simplified, making layout updates and content changes more intuitive, while view transitions smoothly move you from screen to screen as you click.\n\nNew and improved blocks and design features in 7.0 make sites more customizable, with video embed backgrounds in the Cover block, a responsive-enabled Grid block, and new Icons, Breadcrumbs and Heading blocks. An updated Navigation block makes menu changes easier and more reliable in fewer steps. Responsive, mobile-friendly controls in 7.0 allow you to hide or reveal blocks based on screen size, while client-side media handling speeds up media processing. The Font Library screen for managing installed fonts is now enabled for all themes, so site editors are always able to browse, install, and organize fonts. \n\nFor developers, it’s now easier to build modern experiences while staying aligned with Core principles. The new WP AI Client in WordPress 7.0 brings a layer into Core that allows leveraging of AI models from any provider within the WordPress framework. This means plugins and themes can tap into any AI model to expound on its endless options. 7.0 offers even more versatility with the Client Side Abilities API that introduces a standardized way to register and run “abilities” in the browser, supporting richer, more consistent workflows. Additionally, 7.0 introduces PHP-only block registration with auto-generated inspector controls, adding a new dimension to block creation, while Block Bindings updates for pattern overrides expands support to custom dynamic blocks, giving block creators more options.\n\nNeedless to say, this release offers a wide range of flexibility to creators, teams and developers, while bringing a visual refresh to the admin experience you know and love with a fresh default style.\n\n## Work together in real time\n\nBuilding on the momentum started in WordPress 6.9, the ability for teams to create and edit together is more refined and robust in 7.0. With this version of WordPress multiple users can edit and collaborate on the same post or page in real time, with data syncing and stabilized notes for smoother teamwork and a more streamlined editing and review process.\n\n- Real Time Collaboration: Teams can now edit posts and pages together live from multiple locations, with offline editing and data syncing enabled, and a new default HTTP polling sync provider with options for plugins or hosts to include websocket support. With this collaborative content creation workflow, teams can brainstorm more effectively and boost productivity. For the beta period, real-time collaboration is opt-in in order to get broader feedback and testing.\n\n- Notes: 7.0 introduces real time syncing of notes that helps facilitate collaboration, a keyboard shortcut for new notes, and a series of quality-focused fixes that bring more stability to the Notes feature.\n\n## A Refined Admin Experience\n\nWordPress 7.0 gives the wp-admin experience a boost with a fresh default color scheme, and a cleaner, more modern looking dashboard, while keeping the interface familiar. The upgraded dashboard enhances the editing experience with new visual revision comparisons, and smooth transitioning between screens.\n\n- Visual Revisions: Working with revisions is even better in 7.0 with the added ability to make visual comparisons to revision versions within the editor.\n\n- View transitions: Cross-document view transitions in the dashboard offer visual continuity with seamless movement from screen to screen.\n\n## Customizing content with ease\n\nCreators have more flexibility in 7.0 with new tools for content and design, enhanced editing controls, and attention to mobile friendliness. \n\n- Responsive Editing Mode: Block visibility is now more responsive and mobile-friendly, with the ability for blocks to be displayed or hidden based on screen size. \n\n- Pattern Editing and contentOnly interactivity: WordPress 7.0 introduces pattern-level editing modes, a tree view for buttons and list blocks, and the ability to opt out of the default content only mode. The new Spotlight mode helps you isolate content in patterns and notes, while the Isolated Editor mode can be used for editing symbols and reusable pieces like synced patterns, template parts, or navigation. \n\n- Block supports and design tools: 7.0 includes text line indent support, text column support, aspect ratios for wide and full images, dimension width and height support, and dimension presets, tools and controls.\n\n## New blocks and design options at your fingertips\n\n7.0 delivers a series of new and improved blocks and block features, a streamlined navigation workflow, and more versatile design options like video embeds as section backgrounds.\n\n- Navigation Block: Navigation workflow is now more intuitive and clear, with improved editing and presentation. 7.0 introduces customizable navigation overlays as template parts, including mobile version overlays that can be hidden or revealed based on custom breakpoint settings. \n\n- Heading Block: Heading levels are now available as block variations, giving more control over page hierarchy and design.\n\n- New blocks: 7.0 makes building pages more diverse with new Breadcrumbs and Icons blocks.\n\n- Cover block embedded videos: Video embeds can now be used as a background in the cover block, opening up opportunities for sleeker and more creative designs.\n\n- The Grid block is now responsive-enabled allowing grid-based layouts to adapt more smoothly across screen sizes.\n\n- The Gallery block now has lightbox support that lets the user click through and view each gallery image.\n\n## Developer’s toolbox\n\nWorking with WordPress on the backend is now more robust for developers, with new and enhanced API features that support flexibility and lay a foundation for future advancements. The Client Side Abilities API provides a client-side registry for WordPress capabilities that allows you to tap into new and innovative website options. WordPress 7.0 offers even more by introducing the Web Client AI API to Core, enabling access to generative AI models in one central interface.\n\n- Web Client AI API: The new AI client and API acts as a command center for accessing and communicating with generative AI models, with providers remaining external to WordPress Core, and Abilities API integration.\n\n- Abilities and Workflows API: With the new client side abilities package users have access to new and hybrid abilities, filter and search functionality for abilities, and an improved command palette and UI.\n\n- Blocks and patterns created on the server: WordPress 7.0 boasts the ability for PHP-only blocks and patterns to be generated server-side and auto-registered with the Block API.\n\n- DataForm: Introducing a new details layout, new controls (combobox, adaptiveSelect), and updated trigger for panel layout (dedicated edit button). Additionally, the initial iteration for validation is complete: all controls have support, and all layouts display error messages.\n\n- DataViews: DataViews has a new activity layout, and a foundation has been laid to be able to register 3rd party types in future releases.\n\n- CodeMirror update: CodeMirror has been updated to version 5.65.40, aiding more flexible extensibility and library options.\n\n## Media processing in the browser\n\nWordPress 7.0 introduces Client-side media processing, leveraging the browser’s capabilities to handle tasks, like image resizing and compression, for smoother image processing. This enables the use of more advanced image formats and compression techniques, and reduces demand on the web server; providing a more efficient media handling process for both new and existing content, and supporting smoother media workflows.\n\nWith so many options and enhancements in WordPress 7.0 Beta 1, this is still only the beginning. You can expect future releases to be even better.\n\n## Just for you: a Beta 1 haiku:\n\n*As sun kisses moon*,\n\n*Beta 1 ignites in bloom*…\n\n*Seven-oh lands soon*.\n\n*Props to [@ellatrix](https://profiles.wordpress.org/ellatrix/), [@jeffpaul](https://profiles.wordpress.org/jeffpaul/), [@annezazu](https://profiles.wordpress.org/annezazu/), [@chaion07](https://profiles.wordpress.org/chaion07/), [@zunaid321](https://profiles.wordpress.org/zunaid321/), [@audrasjb](https://profiles.wordpress.org/audrasjb/), [@mukesh27](https://profiles.wordpress.org/mukesh27/), [@ankit-k-gupta](https://profiles.wordpress.org/ankit-k-gupta/)*, *[@oandregal](https://profiles.wordpress.org/oandregal/), [@westonruter](https://profiles.wordpress.org/westonruter/), [@karmatosed](https://profiles.wordpress.org/karmatosed/), [@bph](https://profiles.wordpress.org/bph/) for reviewing and collaborating on this post!*","publishedAt":"2026-02-20T15:39:10.000Z","url":"https://wordpress.org/news/2026/02/wordpress-7-0-beta-1/","media":[]},{"id":"rel_MK47jwr-DvSWZppmhE5VL","version":"6.9.1","title":"WordPress 6.9.1 Maintenance Release","summary":"**WordPress 6.9.1 is now available!**\n\nThis minor release includes fixes for 49 bugs [throughout Core](https://core.trac.wordpress.org/query?resolutio...","content":"**WordPress 6.9.1 is now available!**\n\nThis minor release includes fixes for 49 bugs [throughout Core](https://core.trac.wordpress.org/query?resolution=fixed&milestone=6.9.1&group=component&col=id&col=summary&col=milestone&col=owner&col=type&col=status&col=priority&order=priority) and [the Block Editor](https://github.com/WordPress/gutenberg/pull/74806), addressing issues affecting multiple areas of WordPress including the block editor, mail, and classic themes. For a full list of bug fixes, please refer to the [release candidate announcement.](https://make.wordpress.org/core/2026/01/30/wordpress-6-9-1-rc1-is-now-available/)\n\nWordPress 6.9.1 is a short-cycle maintenance release. The next major version of WordPress will be 7.0; it is scheduled for release on 9 April 2026 at [WordCamp Asia](https://asia.wordcamp.org/2026/).\n\nIf you have sites that support automatic background updates, the update process will begin automatically.\n\nYou can [download WordPress 6.9.1 from WordPress.org](https://wordpress.org/wordpress-6.9.1.zip), or visit your WordPress Dashboard, click “Updates”, and then click “Update Now”. For more information on this release, please [visit the HelpHub site](https://wordpress.org/support/wordpress-version/version-6-9-1).\n\n## Thank you to these WordPress contributors\n\nThis release was led by [Aaron Jorbin](https://profiles.wordpress.org/jorbin/) and [Aki Hamano.](https://profiles.wordpress.org/wildworks)\n\nWordPress 6.9.1 would not have been possible without the contributions of the following people. Their asynchronous coordination to deliver maintenance fixes into a stable release is a testament to the power and capability of the WordPress community.\n\n[Aaron Jorbin](https://profiles.wordpress.org/jorbin), [Aaron Robertshaw](https://profiles.wordpress.org/aaronrobertshaw), [acmoifr](https://profiles.wordpress.org/acmoifr), [Adam Silverstein](https://profiles.wordpress.org/adamsilverstein), [Adil Öztaşer](https://profiles.wordpress.org/oztaser), [Aki Hamano](https://profiles.wordpress.org/wildworks), [Alexander Bigga](https://profiles.wordpress.org/albigdd), [amanandhishoe](https://profiles.wordpress.org/amanandhishoe), [Andrew Serong](https://profiles.wordpress.org/andrewserong), [Bernie Reiter](https://profiles.wordpress.org/bernhard-reiter), [brumack](https://profiles.wordpress.org/brumack), [David Arenas](https://profiles.wordpress.org/darerodz), [David Baumwald](https://profiles.wordpress.org/davidbaumwald), [Deepak Gupta](https://profiles.wordpress.org/raftaar1191), [Deepak Prajapati](https://profiles.wordpress.org/deepakprajapati), [Dennis Snell](https://profiles.wordpress.org/dmsnell), [digitalblanket](https://profiles.wordpress.org/digitalblanket), [Ella Van Durpe](https://profiles.wordpress.org/ellatrix), [Fabian Kaegy](https://profiles.wordpress.org/fabiankaegy), [George Mamadashvili](https://profiles.wordpress.org/mamaduka), [Hit Bhalodia](https://profiles.wordpress.org/hbhalodia), [iflairwebtechnologies](https://profiles.wordpress.org/iflairwebtechnologies), [Isabel Brison](https://profiles.wordpress.org/isabel_brison), [Jaydeep Das](https://profiles.wordpress.org/jdeep), [Jb Audras](https://profiles.wordpress.org/audrasjb), [Jeff Golenski](https://profiles.wordpress.org/maverick3x6), [Jeffrey Paul](https://profiles.wordpress.org/jeffpaul), [jhtjards](https://profiles.wordpress.org/jhtjards), [Joe Dolson](https://profiles.wordpress.org/joedolson), [John Blackbourn](https://profiles.wordpress.org/johnbillion), [Jon Surrell](https://profiles.wordpress.org/jonsurrell), [Jonathan Desrosiers](https://profiles.wordpress.org/desrosj), [Jorge Costa](https://profiles.wordpress.org/jorgefilipecosta), [Justin Tadlock](https://profiles.wordpress.org/greenshady), [Karthick](https://profiles.wordpress.org/karthickmurugan), [Kirtikumar Solanki](https://profiles.wordpress.org/solankisoftware), [Lena Morita](https://profiles.wordpress.org/0mirka00), [luisherranz](https://profiles.wordpress.org/luisherranz), [Madhavi Shah](https://profiles.wordpress.org/madhavishah01), [Manuel Camargo](https://profiles.wordpress.org/sirlouen), [Maud Royer](https://profiles.wordpress.org/jillro), [Mehraz Morshed](https://profiles.wordpress.org/mehrazmorshed), [Monarobase](https://profiles.wordpress.org/monarobase), [mrwweb](https://profiles.wordpress.org/mrwweb), [Mukesh Panchal](https://profiles.wordpress.org/mukesh27), [Muryam Sultana](https://profiles.wordpress.org/muryam), [mydesign78](https://profiles.wordpress.org/mydesign78), [Narendra Sishodiya](https://profiles.wordpress.org/narenin), [Nik Tsekouras](https://profiles.wordpress.org/ntsekouras), [Ninos](https://profiles.wordpress.org/ninos-ego), [Noruzzaman](https://profiles.wordpress.org/noruzzaman), [Olga Gleckler](https://profiles.wordpress.org/oglekler), [Ophelia Rose](https://profiles.wordpress.org/gabertronic), [Ov3rfly](https://profiles.wordpress.org/ov3rfly), [Ozgur Sar](https://profiles.wordpress.org/ozgursar), [Paragon Initiative Enterprises](https://profiles.wordpress.org/paragoninitiativeenterprises), [Pascal Birchler](https://profiles.wordpress.org/swissspidy), [Pavel Vybíral](https://profiles.wordpress.org/vybiral), [Peter Wilson](https://profiles.wordpress.org/peterwilsoncc), [pmbs](https://profiles.wordpress.org/pmbs), [Presskopp](https://profiles.wordpress.org/presskopp), [r1k0](https://profiles.wordpress.org/r1k0), [ramonopoly](https://profiles.wordpress.org/ramonopoly), [Riad Benguella](https://profiles.wordpress.org/youknowriad), [Ricardo S.](https://profiles.wordpress.org/ricjcs), [Rolly Bueno](https://profiles.wordpress.org/rollybueno), [Sarah Norris](https://profiles.wordpress.org/mikachan), [Scott Reilly](https://profiles.wordpress.org/coffee2code/), [Sergey Biryukov](https://profiles.wordpress.org/sergeybiryukov), [Shazzad Hossain Khan](https://profiles.wordpress.org/sajib1223), [siliconforks](https://profiles.wordpress.org/siliconforks), [Soyeb Salar](https://profiles.wordpress.org/soyebsalar01), [spielers](https://profiles.wordpress.org/spielers), [Stephen Bernhardt](https://profiles.wordpress.org/sabernhardt), [studio_m](https://profiles.wordpress.org/studiomondiale), [Takashi Irie](https://profiles.wordpress.org/iamtakashi), [Takashi Kitajima](https://profiles.wordpress.org/inc2734), [threadi](https://profiles.wordpress.org/threadi), [Tobias Bäthge](https://profiles.wordpress.org/tobiasbg), [Tomoki Shimomura](https://profiles.wordpress.org/shimotomoki), [Umesh Singh](https://profiles.wordpress.org/umeshsinghin), [Vania](https://profiles.wordpress.org/twvania), [Weston Ruter](https://profiles.wordpress.org/westonruter), [WFMattR](https://profiles.wordpress.org/wfmattr), [wolf45](https://profiles.wordpress.org/wolf45), [zoe20](https://profiles.wordpress.org/zoe20)\n\n## How to contribute\n\nTo get involved in WordPress core development, head over to Trac, [pick a ticket](https://core.trac.wordpress.org/report/6), and join the conversation in the [#core](https://wordpress.slack.com/archives/C02RQBWTW) channel. Need help? Check out the [Core Contributor Handbook](https://make.wordpress.org/core/handbook/).\n\n*Props to *[@audrasjb](https://profiles.wordpress.org/audrasjb/), [@davidbaumwald](https://profiles.wordpress.org/davidbaumwald/), [@westonruter](https://profiles.wordpress.org/westonruter/), [@jeffpaul](https://profiles.wordpress.org/jeffpaul/), [@presskopp](https://profiles.wordpress.org/presskopp/)* for proofreading.*","publishedAt":"2026-02-03T18:07:31.000Z","url":"https://wordpress.org/news/2026/02/wordpress-6-9-1-maintenance-release/","media":[]}],"pagination":{"page":1,"pageSize":20,"totalPages":1,"totalItems":10},"summaries":{"rolling":null,"monthly":[]}}