Tag Archives: 6.0.1

Jb Audras 10:36 pm on July 25, 2022
Tags: 6.0.1, , ,   

A Week in Core – July 25, 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 July 18 and July 25, 2022.

It was quite a busy week, with 121 people contributing to 62 commits!

Worth noting that we never had so many new contributors in a week since we restarted the Week in Core blogposts 2 years ago! 😱😍

  • 62 commits
  • 121 contributors
  • 46 tickets created
  • 6 tickets reopened
  • 49 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 🛠

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

Administration

  • Add labels to read-only form fields – #54302
  • Correct the escaping in documentation lookup for 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 and theme editor – #56007
  • Remove unused CSSCSS Cascading Style Sheets. selectors related to old format menu icons – #35717

Application Passwords

  • Link a more accurate documentation page in User profile edit screen – #56267

Build/Test Tools

  • Add tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.) pattern matching for the testing NPM workflow – #55652
  • Correctly detect the first workflow run for a 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". or tag – #55652
  • Make the 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/ Action pattern matching for tags more specific – #55652
  • Add failure messages for site icon and custom logo tests – #55652
  • Correct the test for passing all expected parameters to the preprocess_comment filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. – #55647, #56244
  • Declare custom-logo theme support for custom logo tests – #55652

Bundled Themes

  • Update NPM dependencies for Twenty Twenty and Twenty Nineteen – #55652
  • Twenty Twenty-One: Add 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. type suggestions to block patterns – #53647
  • Twenty Twenty-One: Rebuild the IE specific stylesheet – #55989
  • Twenty Twenty-One: Update NPM dependencies – #55652

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

  • Add wp_cache_flush_group function – #4476
  • Make the placement of wp_cache_flush_group() more consistent – #55647, #4476

Coding Standards

  • Adjust the logic slightly in wp_ajax_replyto_comment() – #55647
  • Check if the _deprecated_file() function exists in wp-db.php – #56268, #55647
  • Improve variable names in wp-trackback.php – #55647, #56244
  • Move wp-includes/wp-db.php to wp-includes/class-wpdb.php – #56268, #55647
  • Remove extra comma in a compact() call – #55647, #56244
  • Remove unused variable in wp-trackback.php – #55647
  • Rename $comment_post_ID and $comment_author_IP variables in various files – #55647, #56244
  • Replace the old wp-db.php filename in phpcompat.xml.dist – #56268, #55647
  • Standardize on user_id when passing data to comment functions – #55647, #56244
  • Use __DIR__ instead of ABSPATH in wp-db.php – #56268, #55647
  • Use consistent placement for ::prepare_links() methods – #55647

Docs

  • Add a @since note for get_post_permalink() returning false on failure – #45329
  • Add function description and @since mention for get_upload_iframe_src() – #55646
  • Add missing function description in wp-admin/includes/comment.php – #55646
  • Add missing function description in wp-admin/includes/template.php – #55646
  • Document that the $file_format parameter of metadata filters can be null – #55646, #55828
  • Fix indentation issues in block-template-utils.php docblocks, as per docs standards – #55646
  • Fix indentation issues in wp_read_video_metadata and wp_read_audio_metadata docblocks – #55646
  • List the expected type first in a few functions: – #55646
  • Provide a more accurate description for wp_is_theme_directory_ignored() – #56257, #55646
  • Refine @return docblockdocblock (phpdoc, xref, inline docs) mentions for esc_sql(), wp_slash() and wp_unslash() – #53946, #55646
  • Remove an obsolete function description in addslashes_gpc() – #56233, #55646
  • Update do_action() docblock code example – #55977
  • Use third-person singular verbs for function descriptions in block-template.php and block-template-utils.php – #55646
  • Use third-person singular verbs for function descriptions in general-template.php, as per docblocks standards – #55646
  • Use third-person singular verbs for function descriptions in wp-admin/includes/comment.php, as per docblocks standards – #55646

Editor

  • Fix register_block_type does not recognise ancestor block setting – #56184

Embeds

  • Add Pocket Casts as a trusted oEmbed provider – #55860

External Libraries

  • Update the Moment library to version 2.29.4 – #56031

Formatting

Media

  • Allow filtering audio file metadata in wp_read_audio_metadata() – #55828
  • Prevent URLs from overflowing their container in the media editor – #55393
  • enable generating multiple mime types for image uploads; specifically WebP versions for JPEG images by default – #55443

Plugins

  • Improve color contrast on plugins screen when recovery mode is activated – #56190

Posts, Post Types

  • Check if the post type exists in wp_insert_post() – #55877
  • Correct the check for non-existing post in get_post_permalink() – #45329

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 prepare_links method to WP_REST_Post_Types_Controller class – #56019
  • Add prepare_links method to WP_REST_Taxonomies_Controller class – #56020
  • Avoid unnecessarily preparing item links – #52992
  • Prime post caches in comments endpoint – #56272
  • Use wp_get_lastest_revision_id_and_total_count function in WP_REST_Posts_Controller class – #55857

RevisionsRevisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision.

  • Correct the function name for retrieving the last revision ID and total count – #55857
  • Rename the function for retrieving the latest revision ID and total count – #55857
  • Update the “last revision” wording to “latest revision” in various files – #55857

Themes

  • Add a hook to filter theme 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. image URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org – #56180

Upgrade/Install

  • Improve plugin update icon alignment – #56123
  • Upgrade/Install: track php extensions and image library support for WebP and AVIF – #48116

Props

Thanks to the 121 (wow!) people who contributed to WordPress Core on Trac last week: @audrasjb (11), @SergeyBiryukov (11), @peterwilsoncc (6), @timothyblynjacobs (5), @Spacedmonkey (5), @mukesh27 (5), @sabernhardt (4), @mikeschroder (3), @dlh (3), @costdev (3), @desrosj (3), @pento (2), @mitogh (2), @pbiron (2), @dd32 (2), @joedolson (2), @poena (2), @flixos90 (2), @spacedmonkey (2), @johnbillion (2), @rafiahmedd (2), @afercia (2), @kasparsd (1), @dainemawer (1), @karinclimber (1), @cagsmith (1), @seedsca (1), @scofennellgmailcom (1), @jb510 (1), @annezazu (1), @trevorpfromsandee (1), @clorith (1), @grapplerulrich (1), @codekraft (1), @Presskopp (1), @clarkeemily (1), @mxbclang (1), @eugenemanuilov (1), @akshitsethi (1), @tweetythierry (1), @eherman24 (1), @mehulkaklotar (1), @joegrainger (1), @baxbridge (1), @chynnabenton (1), @sobatkras (1), @masteradhoc (1), @isabel_brison (1), @manzoorwanijk (1), @renegeuze (1), @hztyfoon (1), @mattwondra (1), @kebbet (1), @ryokuhi (1), @thakkarhardik (1), @dilipbheda (1), @leogermani (1), @webbeetle (1), @mmaumio (1), @feastdesignco (1), @jeffpaul (1), @markhowellsmead (1), @imarkinteractive (1), @olliejones (1), @garymatthews919 (1), @kwillmorth (1), @barneydavey (1), @tonylocalword (1), @lovor (1), @eatingrules (1), @azaozz (1), @studiolxv (1), @ryan (1), @pbearne (1), @tillkruess (1), @dg12345 (1), @lucasbustamante (1), @dougal (1), @dhilditch (1), @Ste_95 (1), @scribu (1), @sc0ttkclark (1), @filosofo (1), @hellofromTonya (1), @luigipulcini (1), @JustinSainton (1), @Chouby (1), @byohann6 (1), @malthert (1), @mitweka (1), @circlecube (1), @anantajitjg (1), @alamgircsebd (1), @kapilpaul (1), @rachelbaker (1), @furi3r (1), @MatthiasReinholz (1), @helen (1), @whaze (1), @greg24 (1), @onnimonni (1), @dxd5001 (1), @virgar (1), @nuryko (1), @laboiteare (1), @ironprogrammer (1), @zodiac1978 (1), @rodrigosevero (1), @ocean90 (1), @aristath (1), @markoheijnen (1), @gitlost (1), @p_enrique (1), @nunomorgadinho (1), @nacin (1), @targz (1), @NumidWasNotAvailable (1), @nareshbheda (1), @pratiweb (1), @justinahinon (1), and @ryelle (1).

Congrats and welcome to our 41 (!!) new contributors of the week: @dainemawer, @karinclimber, @cagsmith, @scofennellgmailcom, @trevorpfromsandee, @codekraft, @clarkeemily, @mxbclang, @eugenemanuilov, @akshitsethi, @joegrainger, @baxbridge, @chynnabenton, @sobatkras, @masteradhoc, @renegeuze, @mattwondra, @webbeetle, @feastdesignco, @imarkinteractive, @olliejones, @garymatthews919, @kwillmorth, @barneydavey, @tonylocalword, @studiolxv, @dg12345, @dhilditch, @Ste_95, @byohann6, @mitweka, @alamgircsebd, @MatthiasReinholz, @greg24, @dxd5001, @virgar, @nuryko, @laboiteare, @rodrigosevero, @targz, @nareshbheda ♥️

Core committers: @sergeybiryukov (23), @audrasjb (21), @desrosj (8), @spacedmonkey (5), @peterwilsoncc (2), @adamsilverstein (2), and @gziolo (1).

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

Jb Audras 9:42 pm on July 18, 2022
Tags: 6.0.1, , ,   

A Week in Core – July 18, 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 July 11 and July 18, 2022.

  • 17 commits
  • 24 contributors
  • 52 tickets created
  • 3 tickets reopened
  • 57 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 🛠

WordPress 6.0.1 was released last week!

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

Administration

  • Audible messages on AJAX error cases – #54483

Build/Tests Tools

  • Use a consistent way of setting the Administrator role in Ajax tests – #56203

Coding Standards

  • Improve readability of wp-admin/options-permalink.php – #55647
  • Missed space in code indentation in [53707] – #54483
  • Rename the $user_id parameter of get_user_locale() to $user for accuracy – #55647
  • Use MINUTE_IN_SECONDS where appropriate – #55647
  • Use a single input array on Permalink Settings screen – #55647, #55498
  • Improve consistency of punctuation in some strings – #56027

Docs

  • Correct @since tags introduced in WordPress 6.0.1 – #56225
  • Document that allowed_tags() is no longer used in core as of WordPress 4.4 – #55646

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.

  • Remove code from a translatable string in wp-includes/ms-default-constants.php – #56216

Login and Registration

  • Explicitly associate errors with input fields – #54483

Permalinks

  • Add a guiding paragraph on the Permalink Settings screen – #55947
  • Label and describe permalink settings fields – #55498
  • Use home_url() to set the URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org base on Permalink Settings screen – #56235

Posts, Post Types

  • Standardize on $post parameter name where appropriate – #56243, #55647

Users

  • Allow conditional supression of the email notifications that are sent when a new user account is registered – #54874

Props

Thanks to the 24 people who contributed to WordPress Core on Trac last week: @afercia (3), @sabernhardt (2), @costdev (2), @kebbet (2), @SergeyBiryukov (1), @audrasjb (1), @janthiel (1), @pratiweb (1), @hztyfoon (1), @weboccults (1), @Presskopp (1), @NekoJonez (1), @martinkrcho (1), @aristath (1), @poena (1), @johnbillion (1), @tommusrhodus (1), @rishishah (1), @rollybueno (1), @patrickgroot (1), @alexstine (1), @mukesh27 (1), @hasanuzzamanshamim (1), and @peterwilsoncc (1).

Congrats and welcome to our 5 new contributors of the week: @pratiweb, @weboccults, @tommusrhodus, @rollybueno, @patrickgroot ♥️

Core committers: @sergeybiryukov (12), @joedolson (4), and @johnbillion (1).

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

Jb Audras 11:00 pm on July 11, 2022
Tags: 6.0.1, , ,   

A Week in Core – July 11, 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 July 4 and July 11, 2022.

  • 40 commits
  • 64 contributors
  • 65 tickets created
  • 6 tickets reopened
  • 72 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 @covers tags to the taxonomy and category test groups – #39265
  • Add @covers tags to the url test group – #39265
  • Add @coversNothing tags to the tests for some content in documentation and settings files – #39265
  • Add and fix @covers tags to the attachments and 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.-supports test groups – #39265
  • Remove @uses tags from the test suite – #39265
  • Remove duplicate testcase test_get_privacy_policy_url_should_return_empty_when_privacy_policy_page_not_set() from Tests_Url_GetPrivacyPolicyUrl – #39265
  • Separate the tests in basic.php for clarity – #39265, #55652

Coding Standards

  • Apply some alignment fixes after composer format – #55674
  • 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
  • Simplify the logic for setting DB host and port in wpdb::parse_db_host() – #54877, #55647

Comments

  • Use more appropriate escaping functions in class WP_Comments_List_Table – #56101

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

  • Make wp-cron non-blocking for LiteSpeed LSAPI – #54668

Database

  • Ensure 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/. port numbers are numeric in wpdb – #54877

Docs

  • Add missing docblockdocblock (phpdoc, xref, inline docs) description for install_themes_upload() – #55646
  • Add missing function descriptions in wp-admin/includes/update.php – #55646
  • Convert “Application Passwords” to lowercase in WP_Application_Passwords docblocks, for better consistency – #55646
  • Correct the type of the $number parameter in ngettext* filters – #56187
  • Improve description for wp_plugin_update_rows() and wp_theme_update_rows() – #55646
  • Misc. docblock enhancements in WP_REST_Menu_Items_Controller class, as per docblock standards – #55646
  • Typo correction in WP_Application_Passwords docblocks – #56155, #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

  • Include user’s name in the wp_refresh_post_lock() response – #56197
  • Update block editor packages for WordPress 6.0.1 – #56058
  • Update block editor packages for WordPress 6.0.1 – #56058
  • Block Patterns: Update the value used for keywords – #56126

External Libraries

  • Update the Moment library to version 2.29.3 – #56031
  • Update the Underscore library to version 1.13.4 – #56030

General

  • Properly escape home_url() links in wp_page_menu() – #56148

Help/About

  • Add help tab info for the “Send password reset” row action on Users screen – #55801

Media

  • Add tests for wp_img_tag_add_decoding_attr() – #53232
  • Deprecate wp_get_attachment_thumb_file() and Make wp_get_attachment_thumb_url() an alias of wp_get_attachment_image_url()

Menus

  • Use more appropriate escaping functions in class Walker_Nav_Menu_Edit – #56108

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

  • Consolidate menu item type_label schema declaration – #56072

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.

  • Retain default term option when unregistering taxos – #54472

Themes

  • Properly escape home_url() when changing and updating themes – #56145
  • Register the block-templates theme feature – #55681
  • Revert the change of theme preview width on Add Themes screen – #56097. – #54764

Tools

  • Automate backporting core blocks 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/ to Core – #56179

Users

  • Prime user 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. in WP_User_Query class – #55594

Props

Thanks to the 64 people who contributed to WordPress Core on Trac last week: @costdev (10), @SergeyBiryukov (7), @antonvlasenko (4), @ironprogrammer (4), @hellofromTonya (4), @pbeane (4), @zieladam (3), @audrasjb (2), @TimothyBlynJacobs (2), @dilipbheda (2), @johnjamesjacoby (2), @dlh (2), @peterwilsoncc (2), @rudlinkon (2), @jrf (2), @hztyfoon (2), @maximej (1), @sabbirmc (1), @Presskopp (1), @christinavoudouris (1), @grantmkin (1), @chintan1896 (1), @addiestavlo (1), @bernhard-reiter (1), @tobifjellner (1), @jakariaistauk (1), @tushar284 (1), @aniketpatel (1), @sajjad67 (1), @robinwpdeveloper (1), @kebbet (1), @Spacedmonkey (1), @johnbillion (1), @mehulkaklotar (1), @timothyblynjacobs (1), @furi3r (1), @superbthemescom (1), @nathan.noom (1), @ryelle (1), @nacin (1), @markhowellsmead (1), @mukesh27 (1), @csesumonpro (1), @mikeschroder (1), @killua99 (1), @joemcgill (1), @mashukushibiki (1), @mfgmicha (1), @swissspidy (1), @romulodl (1), @JoshuaAbenazer (1), @sergeybiryukov (1), @wonderboymusic (1), @lonnylot (1), @azaozz (1), @obayedmamur (1), @hurayraiit (1), @shraboni (1), @msnewas (1), @im_niloy (1), @cyrillbolliger (1), @azouamauriac (1), @chaion07 (1), and @afragen (1).

Congrats and welcome to our 16 (!) new contributors of the week: @maximej, @sabbirmc, @christinavoudouris, @tushar284, @superbthemescom, @nathannoom, @mashukushibiki, @mfgmicha, @romulodl, @lonnylot, @obayedmamur, @hurayraiit, @shraboni, @msnewas, @im_niloy, @cyrillbolliger ♥️

Core committers: @sergeybiryukov (15), @audrasjb (8), @azaozz (6), @desrosj (5), @peterwilsoncc (4), @gziolo (1), and @spacedmonkey (1).

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

annezazu 4:52 pm on July 5, 2022
Tags: , 6.0.1, ,   

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

zieladam 11:31 am on June 30, 2022
Tags: 6.0.1, , , ,   

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

marybaum 4:13 pm on June 29, 2022
Tags: 6.0.1, ,   

Dev chat 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

annezazu 12:46 am on June 25, 2022
Tags: 6.0.1   

WordPress 6.0.x release team and 6.0.1 schedule

The 6.0.x releases will follow the same consistent minor release leads strategy as the 5.8.x releases and 5.9.x releases did. For the 6.0.1 point releases, the release leads will be:

  • Release LeadRelease Lead The community member ultimately responsible for the Release. / CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. tech: @sergeybiryukov
  • Release Deputy / Editor tech: @zieladam

@zieladam is going to help with 6.0.1 but, for a 6.0.2, there’s an opening if someone is able to help. I’ll keep this post up to date as that changes.

6.0.1 proposed schedule

The following schedule is being proposed for 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).: July 5th, 2022
  • Final release:  July 12, 2022

@sergeybiryukov will run mission control for this release.

TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets update

As of the publish date of this post, 4 Trac Tickets have been fixed and are ready to be backported 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". to be included in 6.0.1. 6 additional tickets either need testing or have a patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. in order to be considered for backporting. 

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/ issues updates

As of the publish date of this post, there are 13 pull requests ready for backporting to the 6.0 branch.

Release coordination

The #6-0-release-leads channel will continue to be used for all coordination and conversation related to the 6.0.x releases. This matches the pattern of communication that worked well for the 5.9.x cycle!

#6.0 #6.0.1