Now Available: WordPress 3.7-4.0 Final Releases

WordPress 3.7.41, 3.8.41, 3.9.40 and 4.0.38 are now available!

These releases feature an update to the upgrade notification to indicate these versions of WordPress are no longer receiving security updates. WordPress 4.1 and later will continue to receive such updates.

The next major version of release of WordPress will be version 6.2 planned for next year.

On sites running WordPress 3.7-4.0 with automatic updates enabled, the upgrade process will begin automatically.

These releases should not be used on new production websites. The latest version of WordPress is available from the downloads page.

Thank you to these WordPress contributors

These releases were led by Josepha Haden Chomphosy and Peter Wilson with Dion Hulse running mission control.

These WordPress releases would not have been possible without the contributions of JB Audras, Colin Stewart, Česlav Przywara, Robin, Jonathan Desrosiers, Linkon Miyan, Mukesh Panchal, Sumit Bagthariya, Matt Mullenweg, Josepha Haden Chomphosy, Peter Wilson, Dion Hulse and the WordPress security team.

As there was no update to the currently stable version of WordPress, version 6.1, these releases were announced here rather than on wordpress.org/news. It was announced on wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ these version of WordPress would cease receiving security updates earlier this year.

Thanks to @costdev for proofreading this post.

#releases

WordPress 6.1.1 RC1 is now available

WordPress 6.1.1 Release Candidaterelease candidate One 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 (RC1) is available for testing! Some ways you can help test this minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality.:

  • Use the WordPress Beta Tester pluginPlugin A 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
    • As this is a minor RCrelease candidate One 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). release, select the Point ReleaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. channel and the Nightlies stream. This is the latest build including the RC and potentially any subsequent commits in trunk.
  • Use WP-CLIWP-CLI WP-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/ to test:
    wp core update https://wordpress.org/wordpress-6.1.1-RC1.zip
  • Directly download the Beta/RC version.

What’s in this release candidate?

6.1.1 RC1 features 28 fixes on Core as well as 18 fixes for the BlockBlock Block 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. Editor (view PRs merged from November 10th onwards).

The following coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. tickets from TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. are fixed:

  • Canonical: Setting a NOT EXISTS tax query in pre_get_posts action triggers a fatal error in wp-includes/canonical.php (#55955)
  • Editor: Massive (potential) performance issues within get_default_block_editor_settings (#56815)
  • Editor: Padding within table cells ignored (#56818)
  • Editor: Creating taxonomyTaxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. https://codex.wordpress.org/Taxonomies#Default_Taxonomies. templates for specific terms are wrongly displayed as not found (#56902)
  • Editor: Separator colors defined using background within theme.json for style variations are ignored (#56903)
  • Editor: Avoid running unnecessary expensive logic around theme.json parsing for classic themes (#56945)
  • Editor: Unable to add blocks on WP 6.1 – “+” button in editor shows up only in certain condition (#56955)
  • Editor: Improve performance of the WP_Theme_JSON class (#56974)
  • Editor: Merge bugfixes from GutenbergGutenberg The 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/ into Core for WP 6.1.1 (#57038)
  • Editor: Fluid typography fixes for 6.1.1 (#57075)
  • Formatting: Check that the Normalizer class exists in remove_accents() (#56980)
  • General: Update to get_page_by_title in 6.1 changes WHERE clause (#56991)
  • I18Ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill.: Fatal error when loading translations early due to a DB error with WPLANG set (#57051)
  • I18N: Always pass $locale to load_textdomain() if we know the localeLocale A locale is a combination of language and regional dialect. Usually locales correspond to countries, as is the case with Portuguese (Portugal) and Portuguese (Brazil). Other examples of locales include Canadian English and U.S. English. (#57060)
  • Media: Featured ImageFeatured image A featured image is the main image used on your blog archive page and is pulled when the post or page is shared on social media. The image can be used to display in widget areas on your site or in a summary list of posts. bugbug A 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. in 6.0.3 (#56855)
  • Media: decoding="async" breaks my site (#56969)
  • Menus: WP 6.1-RC6: menu-item-has-children class is not being applied correctly (#56946)
  • Post, Post Types: WP 6.1 – get_page_by_title(null) returns a page (#57039)
  • Query: WP_Query::the_post causes a type warning when querying for ids, not full post objects (#56948)
  • Query: WP_Query caching discards posts_fields and posts_clauses['fields'] filters. (#57012)
  • Text Changes: Replace instances of “Full site editing” with “Site editor” (#57026)
  • Themes: register_block_core_template_part does WP_Query even on themes that do not support it (#56923)
  • Themes: WP_Theme_JSON_Resolver::get_user_data_from_wp_global_styles call to WP_Query incorrect. (#56900)
  • Themes: Twenty Twenty-Three: visited state of button links use the incorrect text color (#56928)
  • Themes: Reduce usage of wp_get_theme (#57057)
  • Upgrade/Install: Updating plugins with WP6.1 creates .maintenance file and leaves it (#56966)
  • Upgrade/Install: An unupdated Version of Gutenberg Fatally breaks the site on WordPress 6.1 Autoupdate (#56985)
  • Users: cache_users() not defined when calling get_user without field parameter or using all_with_meta or all (#56952)

The following block editor issues from GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ are fixed:

  • Post Featured Image: Fix height/scale overwriting border inline styles (#44213)
  • Fluid typography: add font size constraints (#44993)
  • Allow direct selection of nested Page List block by avoiding dual rendering within block (#45143)
  • Fix popover deprecations (#45195)
  • Components: Refactor ColorPalette tests to @testing-library/react (#44108)
  • Convert the ColorPalette component to TypeScript (#44632)
  • List v2: fix migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. when nested list is invalidinvalid A resolution on the bug tracker (and generally common in software development, sometimes also notabug) that indicates the ticket is not a bug, is a support request, or is generally invalid. (#44822)
  • Link to homeUrl from site editor view menu. (#45475)
  • Table Block: Apply borders and padding on both front end and editor (#45069)
  • Change the order of the pseudo-states in the pseudo selectors array (#45559)
  • Do not look for block variants, if not supporting block-templates (#45362)
  • Restore the empty paragraph inserter (#45542)
  • Cover: Avoid content loss when the templateLock value is all or contentOnly (#45632)
  • List: disable nested list drop zone so dropping list items works (#45321)
  • Switch background color to text color on block separator (#44943)
  • [WP6.1.1] AutoComplete: Revert to event.keyCode to fix IME composition issue (#45704)
  • [WP6.1.1] FormTokenField: Revert to event.keyCode to fix IME composition issue (#45703)
  • Fluid typography: adjust font size min and max rules (#45536)

What’s next?

The developer-reviewed workflow (double committercommitter A 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. sign-off) is now in effect when making changes to the 6.1 branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch"..

The final release is expected on Tuesday, November 15th, 2022. Please note that this date can change depending on possible issues after RC1 is released. Coordination will happen in the WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. #6-1-release-leads channel.

A special thanks to everyone who helped test, raised issues, and helped to fix tickets. With this release candidate, testing continues, so please help test!

The WordPress 6.1.1 release is led by @desrosj, @mamaduka, and @jeffpaul.

#6-1, #6-1-1, #minor-releases, #releases

WordPress 6.1 Release Candidate 6 (RC6) Now Available for Testing

WordPress 6.1 is scheduled for release tomorrow, November 1, 2022! This RC6 release is the last milestone for testing ahead of the official release.

The following issues have been addressed since RC5:

  • Unexpected quotes around search text in custom LIKE queries (see #56933)

This has resulted in a decision to postpone escaping table and field names with wpdb::prepare() to 6.2.

Thank you to all of the contributors who tested the BetaBeta A 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 candidate One 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). releases and provided feedback. Testing is a critical part of making each release strong and a great way to contribute to WordPress.

Installing RC6

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 is recommended that you install RC5 on a test server and site. 

You can test WordPress 6.1 RC6 in three ways:

Option 1: Install and activate the WordPress Beta Tester pluginPlugin A 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 (select the “Bleeding edgebleeding edge The latest revision of the software, generally in development and often unstable. Also known as trunk.” channel and “Beta/RC Only” stream).

Option 2: Direct download the release candidate version (zip).

Option 3: Run the following command to upgrade via WP-CLIWP-CLI WP-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/:
wp core update --version=6.1-RC6

Plugin and Theme Developers

All plugin and theme developers are encouraged to complete testing of their respective extensions against WordPress 6.1 RC6 and update the “Tested up to” version in their readme file to 6.1 this week. If you find compatibility problems, please post detailed information to the support forums, so these items can be investigated promptly.

Review the WordPress 6.1 Field Guide, for more details on this release.

You can find additional information on the entire 6.1 release cycle.

Check the Make WordPress Core blog for 6.1-related developer notes for further details on the 6.1 release.

How to Help Test WordPress

Testing for issues is critical for stabilizing a release throughout its development. Testing is also a great way to contribute to WordPress. If you are new to testing, check out this detailed guide that will walk you through how to get started.

If you think you have run into an issue, please report it to the Alpha/Beta area in the support forums. If you are comfortable writing a reproducible bugbug A 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 file one on WordPress Trac. This is also where you can find a list of known bugs.

Can you speak and write in a language other than English? Help translate WordPress into more than 100 languages!


Haikus for RC6

Table and field name
%i must wait for 6.2 now
Too weird for RC5


Props @annezazu, @marybaum, and @hellofromtonya for peer review.

#6-1, #releases

WordPress 6.1 Release Candidate 5 (RC5) Now Available for Testing

WordPress 6.1 is scheduled for release next week on November 1, 2022! This RC5 release is the last milestone for testing ahead of the official release.

The following issues have been addressed since RC4:

  • get_attached_file(): New call to path_join() can have poor performance on NFS file systems (see #56924)

Thank you to all of the contributors who tested the BetaBeta A 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 candidate One 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). releases and provided feedback. Testing is a critical part of making each release strong and a great way to contribute to WordPress.

Installing RC5

This version of the WordPress software is under development. Please do not install, run, and test this version of WordPress on production or mission-critical websites. Instead, it is recommended that you install RC5 on a test server and site. 

You can test WordPress 6.1 RC5 in three ways:

Option 1: Install and activate the WordPress Beta Tester pluginPlugin A 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 (select the “Bleeding edgebleeding edge The latest revision of the software, generally in development and often unstable. Also known as trunk.” channel and “Beta/RC Only” stream).

Option 2: Direct download the release candidate version (zip).

Option 3: Run the following command to upgrade via WP-CLIWP-CLI WP-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/:
wp core update --version=6.1-RC5

Plugin and Theme Developers

All plugin and theme developers are encouraged to complete testing of their respective extensions against WordPress 6.1 RC5 and update the “Tested up to” version in their readme file to 6.1 this week. If you find compatibility problems, please post detailed information to the support forums, so these items can be investigated promptly.

Review the WordPress 6.1 Field Guide, for more details on this release.

You can find additional information on the entire 6.1 release cycle.

Check the Make WordPress Core blog for 6.1-related developer notes for further details on the 6.1 release.

How to Help Test WordPress

Testing for issues is critical for stabilizing a release throughout its development. Testing is also a great way to contribute to WordPress. If you are new to testing, check out this detailed guide that will walk you through how to get started.

If you think you have run into an issue, please report it to the Alpha/Beta area in the support forums. If you are comfortable writing a reproducible bugbug A 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 file one on WordPress Trac. This is also where you can find a list of known bugs.

Can you speak and write in a language other than English? Help translate WordPress into more than 100 languages!


Haikus for RC5

Here’s two haikus for this final RC.

How about one more?
Getting closer and closer
Have you tested yet?

Last minute backportbackport A port is when code from one branch (or trunk) is merged into another branch or trunk. Some changes in WordPress point releases are the result of backporting code from trunk to the release branch.
Networked storage is tricky
Let’s make it faster


Props @davidbaumwald, @cbringmann, and @jpantani for post publish review, and @mikeschroder for the second haiku.

#6-1, #releases

WordPress 6.1 Release Candidate 4 (RC4) Now Available for Testing

WordPress 6.1 is scheduled for release next week on November 1, 2022! This RC4 release is the last milestone for testing ahead of the official release.

The following issues have been addressed since RC3:

  • Global Styles: Not working for third-party blocks (see #56915)
  • WP_Theme_JSON_Resolver::get_user_data_from_wp_global_styles is incorrectly cached (see #56901)

Thank you to all of the contributors who tested the BetaBeta A 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 candidate One 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). releases and provided feedback. Testing is a critical part of making each release strong and a great way to contribute to WordPress.

Installing RC4

This version of the WordPress software is under development. Please do not install, run, and test this version of WordPress on production or mission-critical websites. Instead, it is recommended that you install RC4 on a test server and site. 

You can test WordPress 6.1 RC4 in three ways:

Option 1: Install and activate the WordPress Beta Tester pluginPlugin A 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 (select the “Bleeding edgebleeding edge The latest revision of the software, generally in development and often unstable. Also known as trunk.” channel and “Beta/RC Only” stream).

Option 2: Direct download the release candidate version (zip).

Option 3: Run the following command to upgrade via WP-CLIWP-CLI WP-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/:
wp core update --version=6.1-RC4

Plugin and Theme Developers

All plugin and theme developers are encouraged to complete testing of their respective extensions against WordPress 6.1 RC4 and update the “Tested up to” version in their readme file to 6.1 this week. If you find compatibility problems, please post detailed information to the support forums, so these items can be investigated promptly.

Review the WordPress 6.1 Field Guide, for more details on this release.

You can find additional information on the entire 6.1 release cycle.

Check the Make WordPress Core blog for 6.1-related developer notes for further details on the 6.1 release.

How to Help Test WordPress

Testing for issues is critical for stabilizing a release throughout its development. Testing is also a great way to contribute to WordPress. If you are new to testing, check out this detailed guide that will walk you through how to get started.

If you think you have run into an issue, please report it to the Alpha/Beta area in the support forums. If you are comfortable writing a reproducible bugbug A 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 file one on WordPress Trac. This is also where you can find a list of known bugs.

Can you speak and write in a language other than English? Help translate WordPress into more than 100 languages!


A Haiku for RC4

One last step needed
Making six point one better
Together we launch


Props @davidbaumwald and @cbringmann for post publish review, and @jpantani for the haiku.

#6-1, #releases

6.1 Product Walk-Through

This summary post provides information regarding the forthcoming live stream walk-through preview of WordPress 6.1. 

Date, Time, and Location

The event will take place on Tuesday, September 13, 2022, at 16:00 UTC via Zoom. Please use this Zoom link to attend. Attendance will require you to be logged into your Zoom account to watch. The event will be recorded and archived for on-demand viewing.

Overview

WordPress 6.1 release squad members will join contributors from #core and the broader WordPress community to conduct an informal preview of the major features in the upcoming release. This Zoom event will include discussion on the new features, resolved tickets, potential blockers, and other topics in a live, public manner.

After the success of the inaugural 6.0 walk-through, this and future releases can expect to see this as a new part of the release cycle.

It’s a fun and simple way to bring more people from the community into the release cycle activities, and preview elements from the upcoming release ahead of the release date. It is also an excellent opportunity to foster open and transparent communication and connect various members, groups, and stakeholders from the WordPress community. 

Participants

Event attendance is open to the general public, and it will be recorded. 

The 6.1 walk-through panel will be composed of a moderator to help guide the conversation among a subset of the WordPress 6.1 release squad members:

Together the panelists will demo features and discuss some of what’s to come in the 6.1 release. The presenters will also answer questions related to the release from attendees if time allows. The recording as well as all questions will be collected and addressed in a follow-up summary post.

For More Information

Please feel free to ask questions about the event’s logistics as replies/comments on this post. If you would like to submit a question ahead of time to be considered for discussion during the event, please share your question in the Make WordPress Slack within the #walkthrough channel.

#6-1, #releases 

Props to all the participants for volunteering, as well as @priethor, @desrosj, @cbringmann, @rmartinezduque, and @dansoschin for helping prepare this announcement and general walk-through readiness.

WordPress 6.0.2 RC1 is now available

WordPress 6.0.2 Release Candidaterelease candidate One 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 (RC1) is available for testing! Some ways you can help test WordPress 6.0.2 RC1:

  • Use the WordPress Beta Tester pluginPlugin A 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
    • As this is a minor RCrelease candidate One 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). release, select the Point ReleaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. channel and the Nightlies stream. This is the latest build including the RC and potentially any subsequent commits in trunk.
  • Use WP-CLIWP-CLI WP-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/ to test:
    wp core update https://wordpress.org/wordpress-6.0.2-RC1.zip
  • Directly download the Beta/RC version.

What’s in this release candidate?

6.0.2 RC1 features 12 bug fixes on Core, as well as 5 bug fixes (view PRs merged from July 5th onwards) for the BlockBlock Block 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. Editor.

The following coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. tickets from TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. are fixed:

The following block editor issues from GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ are fixed:

What’s next?

The developer-reviewed workflow (double committercommitter A 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. sign-off) is now in effect when making changes to the 6.0 branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch"..

The final release is expected on Tuesday, August 30th, 2022. Please note that this date can change depending on possible issues after RC1 is released. Coordination will happen in the WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. #6-0-release-leads channel.

A special thanks to everyone who helped test, raised issues, and helped to fix tickets. With this release candidate, testing continues, so please help test!

The WordPress 6.0.2 release is led by @sergeybiryukov @gziololo

#6-0, #6-0-2, #minor-releases, #releases

#6-0, #minor-releases, #releases

WordPress 6.0.1 RC 1 is now available

WordPress 6.0.1 Release Candidaterelease candidate One 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 (RC1) is available for testing! Some ways you can help testing WordPress 6.0.1 RC1:

  • Use the WordPress Beta Tester pluginPlugin A 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
    • As this is a minor RCrelease candidate One 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). release, select the Point ReleaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. channel and the Nightlies stream. This is the latest build including the RC and potentially any subsequent commits in trunk.
  • Use WP-CLI to test: wp core update https://wordpress.org/wordpress-6.0.1-RC1.zip
  • Directly download the Beta/RC version.

What’s in this release candidate?

6.0.1 Release Candidate 1 features 11 bug fixes on Core, as well as 18 bug fixes (view PRs merged in June & July) for the BlockBlock Block 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. Editor.

The following coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. tickets from TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. are fixed:

  • #55668 – Build/Test Tools: Pass GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ Actions environment variables to the Docker container.
  • #55681 – Fix block-templates theme support not present in /themes REST APIREST API The 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/. endpoint
  • #55808 – About page: Replace video thumbnail image
  • #55837 – Resolve WP_Term_Query cache problem
  • #55890 – Fix caching issues in WP_Term_Query class.
  • #55997 – Remove meetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area. from oembed allow list
  • #56093 – Register Comments Query LoopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop. from metadata to enable title and description translationtranslation The process (or result) of changing text, words, and display formatting to support another language. Also see localization, internationalization..
  • #56097 – Themes: Revert the change of theme preview width on Add Themes screen.
  • #56126 – Block Patterns: Update the value used for keywords.
  • #55810 – Bundled Themes: Revert the Twenty Ten theme version to 3.6.

The following block editor issues from GitHub are fixed:

  • #41423 – Lower the priority of the gallery gap css so it loads after the block layout css
  • #41487 – Add utility classnames back to blocks that have layout attributes specified
  • #41354 – Block Library: Fix JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. Error in AvatarAvatar An avatar is an image or illustration that specifically refers to a character that represents an online user. It’s usually a square box that appears next to the user’s name. Block
  • #40329 – Media & Text: Remove font size declaration from template
  • #41631 – Comment Author and Date blocks: aligned editor markup with the frontend
  • #41328 – Handle no variation case in the block transform menu
  • #40710 – Fix/block metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. icon prop errors
  • #40593 – Prevent opening the links in editor for Latest Posts
  • #40671 – Navigation block “Open on click”: Inherit font style and font weight
  • #41627 – Comments Block: fixed issue with custom font sizes and links color
  • #40560 – Reuse code of the editor placeholder across Post Comments and Post Comments Form
  • #40563 – Improve the logic for warnings for Post Comments Form placeholder
  • #41603 – Post Comments Form: Add button that enables commenting to warning
  • #40799 – Ensure only the main query is modified when resolving template for new posts
  • #40859 – Strip whitespaces in render_block_core_cover before injecting the featured imageFeatured image A featured image is the main image used on your blog archive page and is pulled when the post or page is shared on social media. The image can be used to display in widget areas on your site or in a summary list of posts..
  • #41827 – Post Template: Ensure layout classnames are not attached to inner li elements
  • #41907 – Pasting: Fix performance regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. due to removeWindowsFragments
  • #42131 – Post Comments Form: Fix warning i18ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill.

What’s next?

The dev-reviewed workflow (double committercommitter A 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. sign-off) is now in effect when making changes to the 6.0 branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch"..

As per the proposed WordPress 6.0.1 schedule, the final release is expected on Tuesday, July 12th, 2022. Please note that this date can change depending on possible issues after RC1 is released. Coordination will happen in the WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. #6-0-release-leads channel.

A special thanks to everyone who helped test, raised issues, and helped to fix tickets. With this release candidate, testing continues, so please help test!

The WordPress 6.0.1 release is led by @sergeybiryukov @zieladam.

#6-0, #6-0-1, #minor-releases, #releases

WordPress 6.0 Release Candidate 4 (RC4) Now Available for Testing

WordPress 6.0 is scheduled for release next week on May 24, 2022! This RC4 release is the last milestone for testing ahead of the official release.

You can view changes since the RC3 release via Gutenberg and Trac.

Thank you to all of the contributors who tested the BetaBeta A 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 candidate One 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). releases and provided feedback. Testing is a critical part of making each release strong and a great way to contribute to WordPress.

Installing RC4

This version of the WordPress software is under development. Please do not install, run, and test this version of WordPress on production or mission-critical websites. Instead, it is recommended that you install RC4 on a test server and site. 

You can test WordPress 6.0 RC4 in three ways:

Option 1: Install and activate the WordPress Beta Tester pluginPlugin A 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 (select the “Bleeding edgebleeding edge The latest revision of the software, generally in development and often unstable. Also known as trunk.” channel and “Beta/RC Only” stream).

Option 2: Direct download the release candidate version (zip).

Option 3: Run the following command to upgrade via WP-CLIWP-CLI WP-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/:
wp core update --version=6.0-RC4

Plugin and Theme Developers

All plugin and theme developers are encouraged to complete testing of their respective extensions against WordPress 6.0 RC4 and update the “Tested up to” version in their readme file to 6.0 this week. If you find compatibility problems, please post detailed information to the support forums, so these items can be investigated promptly.

Review the WordPress 6.0 Field Guide, for more details on this release.

You can find additional information on the entire 6.0 release cycle.

Check the Make WordPress Core blog for 6.0-related developer notes for further details on the 6.0 release.

How to Help Test WordPress

Testing for issues is critical for stabilizing a release throughout its development. Testing is also a great way to contribute to WordPress. If you are new to testing, check out this detailed guide that will walk you through how to get started.

If you think you have run into an issue, please report it to the Alpha/Beta area in the support forums. If you are comfortable writing a reproducible bugbug A 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 file one on WordPress Trac. This is also where you can find a list of known bugs.

Can you speak and write in a language other than English? Help translate WordPress into more than 100 languages!


A Haiku for RC4

R-C-4 just shipped
Are you ready for six-oh?
Help us test once more


Thank you to the following contributors for collaborating on this post: @dansoschin, @webcommsat.

#6-0, #releases

6.0 Product Walk-Through

This is a summary post to provide additional information regarding the forthcoming live stream preview/walkthrough of WordPress 6.0.

Date, Time & Link

The event will take place on Tuesday, April 5th, at 15:00 UTC via Zoom here. A link to join will be shared here on the morning of the event, if not sooner. The event will be recorded and archived here for on-demand viewing.

Overview/Background

This will be a first-of-its-kind event whereby the release squad members are joined by various contributors from #core and other teams to conduct a live (via Zoom) walk-through of the major features in the upcoming release. This will include discussion on the new features, resolved tickets, potential blockers, and other topics in a live, public manner.

While the project has had bugbug A 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. scrubs and other types of discussions and meetings as part of the release cycle, a Zoom event is a bit of a new experiment.

This could be a fun and simple way to bring more people into the release cycle from the community and help build early awareness of what’s to come in the release, further ahead of the release date than previously done. This should ultimately enhance communication among various contributor groups and stakeholders within the WordPress community.

Participants

  • Event attendance is open to the general public
  • @daisyo will moderate the event with support from @dansoschin (logistics)
  • Main Panelists (demo’ing features, taking questions)
  • Technical Note Taker (to help with recording bugs or other action items – TBD)

For More Information

Please feel free to ask questions about the event’s logistics as replies/comments on this post. If you would like to submit a question ahead of time to be considered for discussion during the event, please share your question in the Make WordPress Slack within the #walkthrough channel.

#6-0, #releases