A Week in Core – July 4, 2022

Welcome back to a new issue of Week in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. Let’s take a look at what changed on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between June 27 and July 4, 2022.

  • 32 commits
  • 34 contributors
  • 63 tickets created
  • 5 tickets reopened
  • 52 tickets closed

The Core team is currently working on the next major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope., WP 6.1 and on the next minor, WP 6.0.1 🛠

Ticketticket Created for both bug reports and feature development on the bug tracker. numbers are based on the Trac timeline for the period above. The following is a summary of commits, organized by component and/or focus.

Code changes

Build/Test Tools

  • Add support for WP_Error in the test suite’s wp_die() handlers – #55652
  • Correct some GitHubGitHub GitHub is a website that offers online implementation of git repositories that can 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/ Action workflow inline documentation – #55652
  • Enable loopback requests to work on the local development environment – #52708
  • Include the actual _doing_it_wrong() message or deprecation notice in the output – #55652
  • Remove an unused build configuration file – #52604
  • Remove the workflow_run event from the 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/. notification workflow – #56095
  • Run the PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher container with PID > 1 so Ctrl+C works correctly – #55702
  • Update 3rd party GitHub Actions – #55652
  • Update NPM devDependencies to their latest versions – #55652
  • Update the actions/cache action – #55652

Bundled Themes

  • Twenty Eleven: Replace deprecated function calls on theme options page – #54833

Coding Standards

  • Escape the home URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org in the “Background updated. Visit your site” message – #56133
  • Escape the home URL in the “HeaderHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. updated. Visit your site” message – #56132

Comments

  • Use more appropriate escaping functions in class WP_Comments_List_Table#56101

Docs

  • Add @since tags for _doing_it_wrong() and deprecation notice handlers in the PHPUnit test suite – #55652, #55646
  • Add @since tags for wp_die() handlers in the PHPUnit test suite – #55652, #55646
  • Add missing docblockdocblock (phpdoc, xref, inline docs) description for install_themes_upload()#55646
  • Adjust some DocBlocks in wpdb per the documentation standards – #52506, #55646
  • Misc fixes in ShortcodeShortcode A shortcode is a placeholder used within a WordPress post, page, or widget to insert a form or function generated by a plugin in a specific location on your site. APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. function and hook descriptions, as per documentation standards – #55646
  • Update the version in which Meetup.com was removed as an oEmbed source – #55997
  • Use third-person singular verbs for function descriptions in WP_Comments_List_Table class, as per docblock standards – #55646

Editor

  • Alphabetize 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. lists in various places – #56131
  • Ensure only the main query is modified when resolving template for new posts – #56058
  • Register the 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. block from metadata – #56093, #55809
  • Update block editor packages for WordPress 6.0.1 – #56058

General

  • Revert an earlier define of the WPINC constant in src/index.php#54233

Help/About

  • Add help tab info for available row actions in the Media Library – #55800
  • Typo correction in the Media Library help tab text – #55800

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/.

  • Add missing options to the settings endpoint – #56058
  • Use the integer type for page_on_front and page_for_posts options – #56058

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.

  • Pass the $args parameter to all actions and filters in wp_insert_term() and wp_update_term()#55441

Widgets

  • Add a comment in WP_Nav_Menu_Widget::form() to clarify the esc_attr() usage – #56128

Props

Thanks to the 34 people who contributed to WordPress Core on Trac last week: @SergeyBiryukov (5), @costdev (4), @hztyfoon (3), @gziolo (3), @zieladam (2), @Mamaduka (2), @kebbet (2), @mukesh27 (2), @audrasjb (2), @rudlinkon (2), @peterwilsoncc (2), @viralsampat (1), @jameskoster (1), @spacedmonkey (1), @manfcarlo (1), @sajjad67 (1), @ndiego (1), @poena (1), @petitphp (1), @sabernhardt (1), @tomjdv (1), @cu121 (1), @afragen (1), @Presskopp (1), @mboynes (1), @jakariaistauk (1), @robinwpdeveloper (1), @chintan1896 (1), @adamziel (1), @bernhard-reiter (1), @cbravobernal (1), @hasanuzzamanshamim (1), @sandrasanzdev (1), and @aristath (1).

Congrats and welcome to our 7 new contributors of the week: @hztyfoon, @petitphp, @tomjdv, @cu121, @jakariaistauk, @robinwpdeveloper, @sandrasanzdev ♥️

Core committers: @sergeybiryukov (17), @audrasjb (6), @desrosj (5), and @johnbillion (4).

#6-1, #core, #week-in-core

Making the Tech Editor Release Lead Role More Creative and Less Repetitive

Merging 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/ to WordPress on major releases is now more automated than ever.

@zieladam (me) and @gziolo were the tech editor release leads for WordPress 6.0. We’ve quickly noticed that ~30% of the role is about communication and decision making, while ~70% consists of repetitive weekly chores. We want to reverse these proportions.

Most repetitive work falls into one of the two categories:

  • Backporting PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher changes made in the Gutenberg 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 since the previous major WordPress release
  • Releasing weekly 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). versions

Backporting PHP changes made in the Gutenberg plugin since the previous major WordPress release

Finding and backporting all the PHP Pull Requests merged to Gutenberg but not to WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. is a huge task.

For WordPress 6.0, it took us two days just to prepare the list. From there, it was two weeks of pinging, coordinating, reviewing, and merging code before we were done. Furthermore, not all the authors had the availability to help at that point in time.

This cannot be easily automated, but imagine the alternative: Gutenberg developers prepare PRs against WordPress core in parallel with merging their Gutenberg PRs. Any integration issues get surfaced right away, there are fewer merge conflicts, and the release leads don’t have to spend two weeks investigating the commit history and pinging code authors. The future availability of the developers isn’t a problem anymore either.

If that sounds appealing, come and speak up in the ongoing GitHub discussion!

Releasing weekly Beta/RC versions

The weekly release consists of four repetitive tasks:

  • Cherry-pick triaged code to a Gutenberg release 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".
  • Release Gutenberg @wordpress packages from that branch
  • Update the version of packages used in wordpress-develop
  • Manually stabilize any blocks to be included in the new release

@zieladam (me) and @gziolo added a degree of automation to all of the above.

Cherry-pick triaged code to a Gutenberg release branch

Bringing Gutenberg Pull Requests over to WordPress after Beta 1 requires cherry-picking the relevant commits.

Before, this involved manually resolving conflicts and letting the author know. A few times I got confused and spent more time on it than I hoped to.

Today, the new npm run cherry-pick script automates all of that (except resolving conflicts). Furthermore, it can be repurposed for the Gutenberg plugin releases.

Publish the updated @wordpress packages from the release branch

After cherry-picking the relevant changes to the release branch, the way to bring these changes to WordPress core is through npm packages.

Before, it took publishing permissions, a specific local setup, and remembering the correct command with the proper CLICLI Command Line Interface. Terminal (Bash) in Mac, Command Prompt in Windows, or WP-CLI for WordPress. parameters. With all that in place, you ran the built process, waited a longer while, and then published the packages.

Today, this entire process can now be triggered directly from GitHub UI after approval from any Gutenberg core team member.

Update the version of packages used in wordpress-develop

With fresh @wordpress packages published to the NPM registry, the next step is to update the dependencies in wordpress-develop.

Before, it involved a manual synchronization of the new Gutenberg dependencies with the package.jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. file shipped in wordpress-develop. You had to add any new dependencies, update the versions of the existing ones, and delete ones that were no longer used.

Today, the new sync-gutenberg-packages console task automates this effort.

Manually stabilize any blocks to be included in the new release

Finally, a number of steps are required to enable the new stable blocks in WordPress core.

Before, you had to manually list the new blocks in a few .php and .js files and double- or triple-check whether all these lists are in sync. As there are other build steps at play, the resulting Pull Request is quite large. Even though @zieladam and @gziolo were careful, we still ended up making mistakes.

Today, the new sync-stable-blocks console task reduces the entire process to running a single command. All the relevant lists are generated automatically making the process easier and removing any chance for human error.

Next steps

Wiring the above automations to run sequentially would streamline the entire process to a single click of the button:

  • Take a list of Gutenberg PRs as an input
  • Create a Pull Request against wordpress-develop as an output (example)

With the caveat that merge conflicts would still have to be resolved manually.

I’d love to inspire the next release squad to explore this during the 6.1 release cycle.

By simplifying these two large areas, I believe we can truly make the Tech Editor Release LeadRelease Lead The community member ultimately responsible for the Release. role mostly about the decision, communication, and creative work without so many repetitive tasks.

Props to Héctor Prieto (@priethor) and Grzegorz Ziółkowski (@gziolo) for their help in putting this post together.

#6-0-1, #6-1, #core, #core-editor, #gutenberg

Devchat agenda, June 29, 2022

1. Welcome

Last week’s summary

2. Announcements

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/ 13.6 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). 1

3. Blogblog (versus network, site) posts of note

A week in Core, June 27

4. Upcoming releases

The next major is WordPress 6.1.

If you have early tickets, announcements, or you need some help, there’s time here for you.

The next minor is WordPress 6.0.1.

@annezazu has published a team and a schedule!

5. Open floor

Component maintainers with reports have priority. Then, if you have an item, please add it to the comments. If you aren’t going to make the chat, please say so, and the facilitators will bring up your item. If you have a report, the group can post that for you too — again, if a facilitator knows about it.

#6-0-1, #6-1, #agenda

WordPress 6.1 Planning Roundup

WordPress 6.1 will be the third major release of 2022. Following WordPress 6.0 Arturo, 6.1 will aim to refine those experiences found in Arturo and in 5.9 Joséphine [ref]. In preparation, this post includes target dates, features, and a call for the release’s squad.

This release cadence will consist of a long alpha and two short 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. periods before the 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). phase. According to the schedule proposed below and the 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/ release cadence, WordPress 6.1 would include up to Gutenberg 14.1 for a total of 11 Gutenberg releases, the same amount as WordPress 6.0 included.

Proposed WordPress 6.1 Schedule

MilestoneDate
Alpha (trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision. open for 6.1 release)May 3, 2022
Beta 1 & Feature FreezeSeptember 20, 2022
Beta 2September 27, 2022
Release Candidate 1October 4, 2022
Release Candidate 2October 11, 2022
Release Candidate 3October 18, 2022
Dry RunOctober 24, 2022
WordPress 6.1 General releaseOctober 25, 2022

Proposed WordPress 6.1 Release Leads

Release LeadRelease Lead The community member ultimately responsible for the Release.: Matt Mullenweg
Release Coordinator: TBD
CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Tech Lead: TBD
Editor Tech Lead:  TBD
Core Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. Lead: TBD
Editor Triage Lead: TBD
Documentation Lead: TBD
Marketing & Communications Lead: TBD
Test Lead: TBD
Design Lead: TBD

All release decisions will ultimately be this release teams’ to make and communicate while gathering input from the community.

Join The Squad!

If you are interested in being a part of 6.1’s release squad, please show your interest in the comments below. Roles can be shared among more than one person!

#6-1, #planning

Dev chat agenda, June 22, 2022

The weekly meeting of the developers chat will be held in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. 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/. at 20:00 UTC.

1. Announcements

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/ 13.5 lands Wednesday afternoon!

2. Blogblog (versus network, site) posts of note

A Week in Core, from @audrasjb

@matveb‘s post on the Admin experience

What’s new in Gutenberg 13.5? (link to come, since the 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 lands Wednesday at about dev chat time)

Discussion: on disallow assignments in conditions and remove the Yoda condition requirement for PHP. This discussion started on the WordPress Coding Standards (WPCS) repo.

A roadmap to 6.1, also from @matveb

And a YouTube show on FSE and themes.

3. Upcoming releases

The next major is 6.1. @costdev is running early 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: the schedule.

The next minor is 6.0.1. Some tasks for the editor.

4. Open Floor

Are you a component maintainer? Your report, or any ticketticket Created for both bug reports and feature development on the bug tracker. you need eyes on, comes before other items. Especially if you add a comment below!

After components and tickets, the floor is open. If you’re not going to be at the meeting, please say so in your comment, and the facilitators will bring up your item for you. Are there are areas you would like help with or tickets you wish to highlight.

Thanks to @webcommsat for contributing to this agenda.

#6-01, #6-1, #agenda, #core, #dev-chat

Dev Chat Agenda, June 15, 2022

In this post you will find the agenda for the weekly WordPress Developers Chat at June 15, 2022, at 20:00 UTC. All welcome to join the chat in the #Core channel of the Make WordPress 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/..

1. Welcome

Dev Chat summary, June 8, 2022

2. Announcements

3. Blogblog (versus network, site) posts

What’s new in Gutenberg 13.4 (June 10, 2022 post)

A Week in Core – June 13, 2022

Discussion: on disallow assignments in conditions and remove the Yoda condition requirement for PHP. This continues the discussion on the WordPress Coding Standards (WPCS) repo.

4. Upcoming releases

a) WordPress 6.0 ‘Arturo’ Retrospective – the form is open until June 19, 2022

b) Next major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.: 6.1

Early bug scrub schedule for 6.1

c) Next 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.: 6.0.1

6.0.1 Editor Tasks board

5. Core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org.

The first of a number of sprints to help update the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Contributor Handbook will take place on Monday June 20, 2022, 20:00 UTC. All welcome.

A sprint will take place in July in APAC time, more dates to follow.

If you would like to assist with this or have a page of the handbook that you would like to focus on, please contact @marybaum and @webcommsat who are pulling together items for the sprints.

6. Open Floor

If you have any items for Open Floor, please add them in the comments below.

If you are a component maintainer and wish to raise a ticketticket Created for both bug reports and feature development on the bug tracker. in dev chat or give an update, you can also add information in the comments section.

a) Component maintainers – any issues?

b) Tickets to raise?

c) Any other items?

#6-1, #agenda, #dev-chat

Roadmap to 6.1

It’s time to look ahead at the main areas of work for WordPress 6.1. The tune of the release will be to refine the experiences introduced in 5.9 and 6.0, weave the various flows into more coherent and fulfilling experiences for users, maintainers, and extenders, and close some gaps in functionality as we start to look towards Phase 3 of the 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/ roadmap.

Keeping this concise so people can expand through the main Phase 2 project overview.

Template Editor →

Introduce the ability to browse, visualize, and edit the structure of the site. Provide more clarity between global elements (templates, template parts, styles) with the aim of unifying the template editor and the post editor experiences.

There’s a subset of work here around improving the navigation block →

Building With Patterns →

We should be better prepared to fully unlock the potential of patterns as outlined in “Building with Patterns”, which was put together a bit late in the 6.0 cycle. Allow patterns to be a central piece of the creative experience, including tailoring them for custom post types, 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. types, improving the locked down experience, manage saved patterns, etc.

Global Styles →

Blocks & Design Tools →

Continue to make progress on the global styles interface while improving the support for restrictions, privileges, and curated presets. Allow managing webfonts, implement responsive typography, and expand the toolset available to blocks with an eye towards consistency, reliability, and delight.

Themes & Gradual Adoption

There are also several issues around the ability to adopt features like template parts gradually on existing themes, as well as the possibility of getting broader access to theme.jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. editing. It’s also important to continue to look towards theme switching flows and how to best make use of the new possibilities of styles and templates.

#6-1, #gutenberg

Two Weeks in Core – May 30, 2022

Welcome back to a new issue of Week in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. This is a special edition since it exceptionally covers two weeks.

Let’s take a look at what changed on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between May 16 and May 30, 2022.

  • 31 commits
  • 62 contributors
  • 136 tickets created
  • 13 tickets reopened
  • 100 tickets closed

WordPress 6.0 “Arturo” was released !

Ticketticket Created for both bug reports and feature development on the bug tracker. numbers are based on the Trac timeline for the period above. The following is a summary of commits, organized by component and/or focus.

Code changes

AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility)

  • List Tables: Hide the Comments column icon and title attribute from screen readers – #55555, #24766

Administration

  • Fix image overlap in Dashboard welcome panel – #55793

Build/Test Tools

  • Fix comments odd/even instabilities (test leaks) – #54725
  • Link to a specific run attempt in GitHubGitHub GitHub is a website that offers online implementation of git repositories that can 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/ Action 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/. notifications – #55652
  • Temporarily skip MariaDB version test – #55791

Bundled themes

  • Bump versions for WordPress 6.0 release – #55754
  • Revert the Twenty Ten theme version to 3.6 – #55810, #55754
  • Twenty Twenty-Two: Fix typo in Dark Footer pattern docblockdocblock (phpdoc, xref, inline docs)#55772

Code Modernization

  • Replace phpversion() function calls with PHP_VERSION constant – #55680

Coding Standards

  • Correct alignment in various files – #55647

Docs

  • Add missing documentation for fallback_gap_value param – #55567
  • Add missing documentation for some Customize class properties – #55646
  • Correct the type for WP_Post::$post_category and ::$tags_input#55785
  • Explicitly declare some globals for clarity – #51439
  • Use third-person singular verbs for method descriptions in wp-includes/class-wp-roles.php, per the documentation standards – #55646

Editor

  • Fix opinionated 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. styles loading in editor – #55567
  • Return additional block patterns to server-generated settings – #55567
  • Update WordPress packages for 6.0 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). 3 – #55567
  • Update WordPress packages for 6.0 RC 4 – #55567

General

Help/About

  • Add cache busting string to video thumbnail – #55808
  • Ensure about page shows current headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes.#55750
  • Finalise links on about page – #55775

Media

  • Add support for WebP images in the Thickbox library – #55786

Query

  • Check if $wp_query is set in 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. functions – #55722

Quick/Bulk Edit

Site Editor

  • Include style parameter in home template redirect – #55752

Tests

  • Improve the assertions in recommended MySQLMySQL MySQL is a relational database management system. A database is a structured collection of data where content, configuration and other options are stored. https://www.mysql.com/. and MariaDB version tests – #55791, #55652

Themes

  • Accept valid block themes – #55754

Upgrade/Install

  • Update $_old_files for 6.0 – #55794

Users

  • Fail gracefully when checking mapped capabilities without providing the required object ID – #44591

Props

Thanks to the 62 people who contributed to WordPress Core on Trac: @SergeyBiryukov (11), @hellofromTonya (8), @costdev (8), @peterwilsoncc (7), @ryelle (4), @zieladam (4), @sabernhardt (3), @mukesh27 (3), @JeffPaul (2), @ironprogrammer (2), @desrosj (2), @hellofromtonya (2), @audrasjb (2), @johnstonphilip (2), @azaozz (2), @ravipatel (2), @ryokuhi (1), @karlgroves (1), @grantmkin (1), @mamaduka (1), @iamjaydip (1), @passoniate (1), @jeherve (1), @afercia (1), @ilunabar (1), @henry.wright (1), @johnbillion (1), @aristath (1), @mattheweppelsheimer (1), @azouamauriac (1), @Ninos Ego (1), @TobiasBg (1), @wpsmith (1), @GaryJ (1), @nacin (1), @jsnajdr (1), @poena (1), @jrf (1), @Boniu91 (1), @dd32 (1), @davidbaumwald (1), @Chouby (1), @nalininonstopnewsuk (1), @webcommsat (1), @marybaum (1), @meher (1), @wparslan (1), @annezazu (1), @critterverse (1), @vdankbaar (1), @FlorianBrinkmann (1), @thijso (1), @teunvgisteren (1), @timkersten655 (1), @omaeyusuke (1), @ayeshrajans (1), @graham73may (1), @jffng (1), @mehedi890 (1), @sergeybiryukov (1), @gziolo (1), and @ndiego (1).

Core committers: @sergeybiryukov (14), @peterwilsoncc (7), @gziolo (5), @hellofromtonya (2), @ryelle (1), @desrosj (1), and @audrasjb (1).

#6-1, #core, #week-in-core