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

Core Editor Improvement: Advancing the writing experience

These “CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Editor Improvement…” posts (labeled with the #core-editor-improvement 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.)) are a series dedicated to highlighting various new features, improvements, and more from Core Editor related projects. 

The experience of writing your latest post, whether as part of your weekly routine or out of excitement from a recent adventure, just got easier in many different ways. From a new mode that helps you focus on just writing to more keyboard shortcuts for quickly navigating content, there’s something for everyone, no matter how you approach writing your posts. 

For clarity, everything that will be included in the 6.1 release is explicitly noted below. Otherwise, it is available in 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/ 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 exactly what you want (available in WordPress 6.1)

After the introduction of multi-select, where you can select text across multiple blocks without selecting the blocks as a whole, new enhancements were introduced to balance against situations where you might want to select across blocks. Specifically, partial selection remains the default option until you select a 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. that can’t be combined, like an Image block. Tied to this, the animation and appearance of the overall experience were also updated to be clearer and smoother. You can see this at play in the visual below, where partial selection is used until an image is selected and the overlay selection color switches to every block.  This should make both the feeling of selecting blocks and the accuracy of doing exactly what you want much more cohesive. 

GIF showing text being selected at first across individual paragraph blocks before, when selecting an image block, all blocks being selected.

Move faster with keyboard shortcuts (available in Gutenberg 14.3)

Gutenberg 14.3 included support for alt + arrow keyboard combinations to make navigating blocks of text quick and easy:

  • If your cursor is at the end of a long paragraph, you can press the alt + up arrow to move to the beginning of that paragraph. 
  • If you are already at the beginning of a text block, you can press the alt + up arrow to move to the start of the previous paragraph. 
  • If you press alt + down arrow, it will move you to the end of a block of text.

Improved document settings (available in WordPress 6.1)

A revamped document settings experience improves legibility and resulting usability with a cleaner, more organized display. It should help you more readily access all the important information about your post/page, including the template picker and scheduler. Specifically, the fields for post format, slug, template, and authors are aligned and have the same width. The template displays ‘default template’ instead of none, and the Permalink link opens a popover to edit the slug when clicked. The result is a cleaner, more organized display so you can see exactly what you need to before sharing your next post. 

Before and after images next to each of changes to document settings with the after image showing more consistency.

Do more with the Quote & List blocks (available in WordPress 6.1)

The Quote block now allows you to add nested blocks, meaning you could add the new List block inside the new Quote block. Similarly, the List block uses inner blocks, meaning your list items can be easily sorted and indented with a much-improved user experience.

Quote block with multiple inner blocks listed, including image and list.

Opt in to fewer distractions and more focus (available in Gutenberg 14.4)

For those looking for an even more focused experience, enter distraction-free mode available as soon as Gutenberg 14.4 is released. It’s a more drastically reduced experience with the following settings in place, allowing you to focus on the creation experience as much as possible: 

  • Hides the top toolbar until one intentionally hovers over where it typically sits.
  • Removes many top toolbar buttons.
  • Automatically closes any open sidebars, from block settings to list view. 
  • Hides the insertion point indicator, reducing visual clutter. 
  • Hides the block toolbar. 

More work remains to be done to fully form this new mode but the promise of what it provides is exciting for those looking for a more contained writing experience.

Use the autocompletion for links anywhere you want (available in WordPress 6.1)

While the [[ shortcut was introduced a while ago, it can now be used anywhere you want to add any internal link you’d like. Previously, it was isolated to just the blocks that explicitly opted in, and as you can see in the video below, you can now take advantage of this feature no matter what you’re editing:

Transform blocks with ease with improved organization (available in WordPress 6.1)

The transforms menu offers a shortcut to switch to different blocks, depending on your content. As the number of blocks has grown and the reliance on this menu has increased, the menu’s organization has evolved to emphasize content blocks. Specifically, blocks that support paragraph, heading, list, and quote transforms, are now weighted over other more structural blocks, like a Group or Column. This should help common pathways be easier to find as more common transformations. 

Heading block transform menu open showing prioritized content blocks.

Keep List View open by default (available in WordPress 6.1)

For any List View fans, Gutenberg 13.3 introduced the option to have List View open by default. This makes navigating complex content, like a long post sharing every detail of a big adventure, much easier. Rather than needing to open it every single time you enter the editor, it’ll be waiting for you with every new post you write:

Preferences modal open showing "always open list view" checked off.

Enjoy improvements to the various inserters (available in Gutenberg 14.2)

The inserters are a big part of the base experience of using the block editor. An update to the animation effect for the sibling and in-line inserters now offers a more natural and responsive feel. On the flip side, when you’re typing, the block inserter is now hidden to reduce visual noise and allow more of a focus on the writing experience itself: 

Taken together, these enhancements will allow you to engage with the inserters better only when you need them. 

Control image captions from the block toolbar (available in Gutenberg 14.4)

You can now add or remove a caption for an image directly from the block toolbar. If a caption has already been set, it will be included by default when the image is added to your content, saving you time and giving you options.

More to come

Ensuring the base editing experience is excellent is always a work in progress and a focus, especially as work is underway to bring the block editing experience to more parts of the site for more people. As you run into bugs, feature requests, or feedback, please remember to share in GitHub so the experience can continue to be refined. 

#core-editor-improvement, #gutenberg

Dev Chat summary, October 27, 2022

Notes from the weekly WordPress developers chat held in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. channel on 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/..

Start of the meeting on Slack.

The meeting was led by @marybaum and @webcommsat.

1. Welcome

Agenda followed for the meeting.

Summary from dev chat on October 19, 2022 thanks to @marybaum.

2. Announcements

Today is the last dev chat before 6.1 launches on Tuesday.

WordPress 6.1 Release Candidate 3 is now available. Thank you to everyone who supported this and to the testers at the release party.

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

@audrasjb gives a summary and thanks all the people involved on core tickets in the latest A Week in Core.

@priethor has published a guide to the final release process. You can start testing and other preparations for the big day now!

@sabernhardt discusses some new markup and styles in the world of Multisite.

@estelaris showcases a new design for HelpHub.

Gutenberg 14.4 has been released by first-time release leadRelease Lead The community member ultimately responsible for the Release. @JuanMe and is available in the plugin repo – Make blog post will be published tomorrow.

4. Releases

The following updates on 6.1 were shared or received by the release squad members.

@desrosj: two issues have been identified as potentially necessary fixes for an 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). 4 (RC4), which is safe to anticipate at some point tomorrow.

Update from October 27, 2022: @desrosj and @priethor referred to the Release Day process post. This Release Day post will be kept updated as needed.

5. Components and tickets

a) @sergeybiryukov: Upgrade/Install component: Bringing attention again to the call to action for testing the Rollback feature on make/hosting.

Build/Test Tools component: A new workflow was introduced for testing and building default themes. Thanks @desrosj and @peterwilsoncc! Visit ticketticket Created for both bug reports and feature development on the bug tracker. #56898 for more details.

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. component: A performance issue in WP_Textdomain_Registry was identified and resolved. Thanks @swisspidy, @flixos90, @jonnyharris (check id), @ocean90, @costdev. More details on ticket #39210.

Date/Time, General, Permalinks component: No major news this week.

b) Testing 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 Dependencies

@afragen gave a reminder on the call to action for testing Plugin Dependencies. He requested feedback from hosting companies who have not as yet replied on the Rollback Updater Failure. The full discussion can be read in Slack – please note that there are some message threads as part of this discussion too.

@hellofromtonya added: “The goal is to collect data and feedback on shared web hosting platforms to address concerns. As many web hosts can get involved, the better.”

c) Mary shared a message from @nalininonstopnewsuk: Nalini has been supporting a new contributor, @Robin, who wants to get more involved with the project. He is interested in helping with the components, after coming to dev chat and hearing about them. He may be able to help with the login/ registration component. Nalini has suggested he comes along with her to some scrubs for the Quick/ Bulk Edit component and follows some tickets to learn more about components and TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress.. She also asks if a maintainer in the APAC timezone would be able to share with this contributor how they maintain a component. There is currently no maintainer for the login/ registration component.

6. Open Floor

@pbiron drew attention to a discussion in core earlier in the week. Read the discussion in full in the Make WordPress Slack. The discussion focused on changes to the plugin that are not released into the wild in the form of a 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 for any testing/confirmation before being ported over for inclusion in Core (especially for a 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. during 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).).

Props to: @webcommsat for the dev chat summary, and to @marybaum for review.
Thank you too to those who confirmed various sections.

#6-1, #dev-chat, #summary, #week-in-core

What’s new in Gutenberg 14.4? (26 October)

“What’s new in 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/…” posts (labeled with the #gutenberg-new 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.)) are posted following every Gutenberg release on a biweekly basis, discovering new features included in each release. As a reminder, here’s an overview of different ways to keep up with Gutenberg and the Full Site Editing project.


Gutenberg 14.4 has been released and is available for download!

It introduces a distraction-free mode for text-based content creation, it redesigns the main pattern inserter, it continues to improve recent responsive design features such as Fluid Typography and much more!

Fun fact: Johannes Gutenberg invented the printing press in 1440 and this version of Gutenberg is the 14.4.0

Table of Contents

Explore easier navigation and larger previews of patterns in the Inserter

A new design offers a split view between categories and patterns, improving the navigation between categories and providing larger previews for patterns, resulting in improved discoverability and at a glance context.

Enjoy distraction free writing

Gutenberg 14.4 includes a new mode that reduces various parts of the editor interface, allowing for a more focused writing experience. When enabled, the sidebars are closed and toolbars fade away, leaving your content to take center stage. You can toggle this mode on/off as you’d like, depending on what you’re looking for.

Control image captions from 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. toolbar

With this release, you can now add or remove a caption for an image directly from the block toolbar. If a caption has already been set, it will be included by default when the image is added to your content.

Lock the ability to edit the navigation block

The Navigation block offers an additional option when locking to restrict the ability to edit the content on its inner blocks (links and submenus). This helps further curate the experience, especially if you’re taking advantage of the ability to use block template parts in classic themes.

Lock modal open for the navigation block with all options locked, including the ability to edit a block.

Take advantage of improvements to Fluid Typography

In Gutenberg 13.8, Fluid Typography for font size presets was introduced to allow themers to generate fluid font size presets in 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.. This release of Gutenberg builds on this work by automatically converting custom font sizes to fluid values when fluid typography is enabled.

Changelog

Enhancements

  • Add prop to disable block selection clearer in BlockList. (44517)
  • Multi-select: Fix 1px indent. (44709)
  • ServerSideRender: Add new skipBlockSupportAttributes prop. (44491)
  • Tag Processor: Add get_updated_html as a non-toString method of stringifying the markup. (44597)
  • Try: Add a small radius to the multi selection style. (44708)
  • Rich Text: Use fallback icon for highlight format. (44705)
  • Create Block: Allows custom keys to be generated in block.json files and package.json files. (44649)

Block Library

  • Comments: Add spacing support. (45102)
  • Tag Cloud: Add typography supports (except font size). (43452)
  • Block Locking: Adds content locking to the navigation block. (44739)
  • Image: Add toolbar button to add a caption. (44965)
  • List Item: Adopt typography supports. (43312)

Components

  • BorderBoxControl: Omit unit select when values are mixed. (44592)
  • SuggestionList: Use requestAnimationFrame instead of setTimeout when scrolling selected item into view. (44573)

Block Editor

  • Introduce distraction free mode. (41740)
  • Redesign the main pattern inserter. (44028)
  • Inserter: Add a more pronounced hover effect. (44711)

Design Tools

  • SpacingSizesControl: Increase slider’s max value to 300. (44956)
  • Style engine: Permit wp custom CSSCSS Cascading Style Sheets. properties. (43071)
  • Try color theming. (44668)
  • Global Styles: Modify Frame animation of styles grid. (39717)

Bug Fixes

  • Clickable placeholder upload button. (44817)
  • Insertion point showing up unexpectedly. (44702)
  • Overflowing patterns. (44853)
  • Inspector is usable on the top level block even if it is content locked. (44878)
  • Use active variation as the parent block if available. (44609)
  • Placeholder for the navigation link label, to be about the label. (44733)
  • Hide the inbetween inserter consistently as you move the mouse. (44814)
  • Margin visualiser: Apply negative value to margins with calc(). (44718)
  • Placeholder: Fix hover style. (44701)
  • Post editor: Rename view to Preview. (45074)
  • Prevent empty block toolbars from showing empty slots. (44704)
  • Use inert attribute instead of useDisabled. (44865)
  • cleanForSlug: Replace multiple hyphens with a single one. (44873)
  • Block Popover: Fix incorrect positioning of padding and margin visualizers on scroll. (44998)
  • Most used tags: Try fixing label. (44859)
  • Only include theme.css if the theme declares support for wp-block-styles. (44640)
  • Merge inner blocks if wrappers are equal. (43181)
  • Try nested patterns previews with block editor setting. (44784)
  • Design Tools Adjust the custom range steps to match the units chosen. (44959)
  • Global Styles: Invoke zoomed-out view when selecting a style variation. (44987)

Block Library

  • Avoid querying block templates during installation. (44584)
  • Buttons: Add specificity for the editor. (44731)
  • Embed Block: Add support for Tumblr Dashboard URLs. (44854)
  • Fix list outdents on Enter in quote block. (44809)
  • Fix the cover block focal point picker. (44991)
  • Fix typo for word occurred. (44914)
  • Fix visibility of nested Group block appender. (45050)
  • Fix: Follow discussion settings in the comments block edit. (44463)
  • Group, Row, Stack, Columns. Fix missing border 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.. (44696)
  • List Item: Allow Gutenberg to override coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. block type. (44911)
  • List v2: Selection when creating paragraph from empty list item. (44864)
  • Remove anchor support from the navigation block. (44721)
  • Removes __unstableMaxPages attribute from Page List block (and Nav block). (44415)
  • Site Logo: User permission HTTPHTTP HTTP is an acronym for Hyper Text Transfer Protocol. HTTP is the underlying protocol used by the World Wide Web and this protocol defines how messages are formatted and transmitted, and what actions Web servers and browsers should take in response to various commands. errors. (45104)
  • Site logo: Centered state, for upload button. (44861)
  • Media: Cover block text color heuristic for cross origin media. (44552)
  • Icons: Arrow icons being misaligned. (44666)
  • Patterns: Hide list items from content area of content locked blocks. (44676)
  • Templates 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.: Avoid PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher warning when getting dynamic template data. (44783)
  • Block Settings: Show move to on nested blocks when only one root block. (44827)
  • Navigation: Fallback to a classic menu if one is available. (44173)

Site Editor

  • Toggle Navigation Menus SidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme.. (44860)
  • Zoomed out view: Keep list view open when entering mode. (44781)

Block Editor

  • Cover: Fix erroneous focus style in editor. (44707)
  • Native inner blocks merge where appropriate. (45048)

Typography

  • Fluid typography: Convert server-side block support values. (44762)
  • Fluid typography: Covert font size number values to pixels. (44807)
  • Fluid typography: Ensure fontsizes are strings or integers. (44847)
  • Font Size Picker Hint: Fallback to font size slug if name is undefined. (45041)
  • Make custom font sizes appear fluid in the block editor when fluid typography is enabled. (44765)
  • Search block: Ensure font sizes values are converted to fluid in the editor. (44852)
  • Fluid typography: Convert font size inline style attributes to fluid values. (44764)

Components

  • FontSizePicker: Fix 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. order in RTL languages. (44590)
  • Navigator: Restore focus only once per location. (44972)
  • Spacing Sizes Control: Try improving layout spacing. (44858)

Global Styles

  • Ensure style card effect doesn’t cause scrollbars to appear. (44823)
  • Fluid Typography: Fix 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 global styles where fluid clamp rules were not calculated for custom values. (44761)

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)

Performance Benchmark

The following benchmark compares performance for a particularly sizeable post (~36,000 words, ~1,000 blocks) over the last releases. Such a large post isn’t representative of the average editing experience but is adequate for spotting variations in performance.

Post Editor

VersionLoading TimeKeyPress Event (typing)
Gutenberg 14.414.9s78.81ms
Gutenberg 14.315.3s84.59ms
WordPress 6.110.4s38.95ms

Site Editor

VersionLoading TimeKeyPress Event (typing)
Gutenberg 14.41.5s77.73ms
Gutenberg 14.34.7s75.05ms
WordPress 6.17.6s41.51ms

Contributors

The following contributors merged PRs in this release:

@aaronrobertshaw @adamziel @afercia @ajlende @alanjacobmathew @amustaque97 @andrewserong @annezazu @BE-Webdesign @benridane @c4rl0sbr4v0 @carolinan @chad1008 @ciampo @costdev @danielbachhuber @dcalhoun @desrosj @dinhtungdu @draganescu @ellatrix @fabiankaegy @fluiddot @geriux @getdave @glendaviesnz @gvgvgvijayan @jasmussen @jeremylind @jorgefilipecosta @joshuatf @jrfnl @jsnajdr @kevin940726 @Mamaduka @mikachan @mirka @mtias @noisysocks @ntsekouras @oandregal @ockham @pento @PooSham @ramonjd @ryanwelcher @sabernhardt @SantosGuillamot @scruffian @Soean @t-hamano @talldan @tellthemachines @thelovekesh @tyxla @walbo @youknowriad

The following PRs were merged by first time contributors:

  • @benridane: Fix list outdents on Enter in quote block. (44809)
  • @jeremylind: FIX: Typo in block.json schema default scope values. (44944)
  • @PooSham: Add support for ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/. 18 and later to jest-preset-default. (44680)
  • @thelovekesh: package(prettier-config): Update documentation. (44620)

Kudos to all the contributors that helped with the release! 👏

Thanks to @priethor and @annezazu for their assistance with the release, and props to @javiarce for the images and videos!

#block-editor, #core-editor, #gutenberg

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

Dev Chat agenda: October 26,2022

1. Welcome

October 26 is the last dev chat of the 6.1 release cycle. Next week at this time, 6.1 will be live!

2. Announcements

WordPress 6.1 RC3 landed on Tuesday, October 25. Please download and test!

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

@audrasjb thanks all the people in the latest A week in Core.

@priethor has published a guide to the final release process. You can start testing and other preparations for the big day now!

@sabernhardt discusses some new markup and styles in the world of Multisite.

And @estelaris showcases a new design for HelpHub.

4. Upcoming releases

The next major is 6.1.

An impromptu 6.0.3 minor landed last week. The CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team also updated every version below 6.0 that is still under official support.

5. Components and tickets

@robinwpdeveloper, a developer in Bangladesh, has volunteered to maintain the Login/Registration component. He got inspired by this October 5 devchat thread and messaged @marybaum on October 23.

6. Open Floor

Got something to raise? Add it to the comments, and see you at devchat!

#agenda, #core, #dev-chat

Performance Chat Summary: 25 October 2022

Meeting agenda here and the full chat log is available beginning here on Slack.

Announcements

Focus area updates

  • @mxbclang: Results of focus area updates vote
    • Added new Database focus area – see GH label and Project
    • Renamed JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/. focus area to JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. & CSSCSS Cascading Style Sheets. – see GH label and Project
    • Removed Site Health focus area – added “LEGACY” to GH label and Project and moved all active issues to an appropriate new focus area
    • Working on adding a list of focus areas to the Handbook
    • Call for leads for Database – @olliejones volunteered! Will update GH accordingly

Images

@adamsilverstein @mikeschroder

GitHub project

Feedback requested

Object Cache

@tillkruess @spacedmonkey

GitHub project

  • No updates

Feedback requested

Measurement

N/A

GitHub project

  • We’re seeking 1-2 POCs for this group; if you’re interested, please comment here or pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” in 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/.
  • @mxbclang: Work continuing on defining 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 Checker plugin and getting close to engineering; more updates soon

Feedback requested

JS & CSS

@aristath @sergiomdgomes

GitHub project

  • No updates

Feedback requested

Database

@olliejones

GitHub project

  • No updates

Feedback requested

Infrastructure

@flixos90

GitHub project

  • @flixos90: Planning to get back to the Server-Timing 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. work this week and reviewing focus area updates in https://github.com/WordPress/performance/pull/566 today

Feedback requested

Open Floor

  • @flixos90: Identified and validated the main cause of the 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. with @spacedmonkey and it has been fixed. Will run another iteration of the same analysis for 6.1-RC3 today or tomorrow to verify that results have improved.
    • @olliejones: What was it?
    • @flixos90: Was caused by a bug in https://core.trac.wordpress.org/ticket/39210. Research has not yet been published as wanted to see how the situation evolves, but fair to say that we got the perfect outcome and it shows how important performance analyses are. Will write a summary with concrete numbers up next week and publish after 6.1 launch.

Our next chat will be held on Tuesday, November 1, 2022 at 12pm EDT in the #core-performance channel in Slack.

#core-js, #core-media, #performance, #performance-chat, #summary, #hosting-community

#meta

WordPress 6.1 Release Day Process

Preparation for WordPress 6.1 final release is underway. This post shares the release process, including the timeline and how you can help. The post will be kept up to date as the release process evolves.

Release Timeline Overview

The current plan is:

Edit History


Dry Run 📅

The Dry Run is a key event as a final walk-through for the final release. As noted above, the current plan is to start it on 2022-10-31 14:00. You are invited to observe and/or participate. It’ll happen in the #core Slack channel.

What happens during the dry run?

  • Review 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. reports to determine if any are critical to warrant another 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 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).).
  • Checks and any necessary updates are made in the src/wp-admin/includes/update-core.php file.
  • Pre-release scripts are run to ensure test suites, coding standards, and other automated checks pass.

If the results are acceptable, the release goes into a 24-hour code freeze period.

24-Hour Code Freeze

After the dry run and before the release party starts, a mandatory 24-hour code freeze goes into effect.

What does this mean? No source code for 6.1.0 (i.e., in 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".) can be changed during these 24 hours.

What happens if a critical bug is reported during this period? The release squad will meet with committers and maintainers to determine if the issue is a blockerblocker A bug which is so severe that it blocks a release..

  • If yes, another RC release happens, and the release process restarts (meaning the dry run is repeated, and then the 24-hour code freeze clock restarts).
  • If not, then the bug is targeted for 6.1.1.

The Stable Release Party

As noted above, the release party on November 1st will start no sooner than 24h after the code freeze starts, with the exact time to be determined accordingly. You are invited to observe and/or participate. It’ll happen in the #core Slack channel.

The release party walks through the steps in the Major Version Release process for anyone who wants to follow along.

Please note releasing a major version requires more time than releasing a 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. or release candidate. There are more steps in the process. If any last-minute issues need addressing, more time will be needed.

How You Can Help

A key part of the release process is checking that the ZIP packages work on all the different server configurations available. If you have some of the less commonly used servers available for testing (IIS, in particular), that would be super helpful. Servers running older versions of PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher and 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/. will also need testing.

You can even start this early by running the WordPress 6.1 RC3 packages, which are built using the same method as the final packages.

During the release party, options will be provided on how to help test the release package.

Tips on What to Test

In particular, testing the following types of installs and updates would be much appreciated:

  • Does a new WordPress install work correctly? This includes running through the manual install process, as well as 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/ or one-click installers.
  • Test upgrading from 4.0.37, 4.9.22, 5.8.6, 5.9.5, 6.0.3, and 6.1 RC3, as well as any other versions possible.
  • Remove the wp-config.php file and test a fresh install.
  • Test single site and multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site/networknetwork (versus site, blog) (both subdirectory and subdomain) installations.
  • Does it upgrade correctly? Are the files listed in $_old_files removed when you upgrade?
  • Does multisite upgrade properly?

Testing the following user flows on both desktop and mobile would be great to validate each function as expected:

  • Publish a post, including a variety of different blocks.
  • Comment on the post.
  • Install a new 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/theme, or upgrade an existing one.
  • Change the site language.
  • If you’re a plugin developer, or if there are complex plugins you depend upon, test that they’re working correctly.

Props to @desrosj and @zoonini for peer review.

#6-1, #core, #release-process

Editor chat summary: Wednesday, 20 October 2022

This post summarizes the weekly editor chat meeting on Wednesday, 20 October 2022, 14:00 UTC held in Slack.

WordPress & 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/ releases

WordPress 6.1

WordPress 6.1 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). was released yesterday from the editor side things are going smoothly.

WordPress 6.0.3 & 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 14.3.1.

There were some security issues fixed and included in the 6.0.3 release and release for all the lower versions with auto-updates. Some of these fixes were editor related, so a new version of Gutenberg was also released 14.3.1.

Please ensure that all your websites have Gutenberg and coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. updated!

Key project updates

Site Editor

There is a big PR in progress that redesigns the UIUI User interface, introduces a browse mode, and makes things much more intuitive for end users. Please leave your feedback at #44770.

Building with patterns project

The Gutenberg team merged a redesign to the pattern inserter #44028. With the aim of making it more user-friendly.

WordPress 6.2

@annezazu shared the following on the agenda:

Before a 6.2 roadmap post similar to the ones that have come before is shared, lots of work has been done to revamp the following issue to make it the source of truth for the months ahead: https://github.com/WordPress/gutenberg/issues/33094 If you’re looking for ways to help in the coming months, please take a look at this issue and know it’ll be kept up to date! You’re also welcome to join a hallway hangout in the FSE Outreach Program

Please have a look into the issue and in case there is any feedback leave a comment!

@jorgefilipecosta added:

Thank you @annezazu for sharing this with us ensuring the issue will keep being updated!

It is good to have a single issue as the main source of truth for the work that will be done in the coming months.

Let’s try our best to ship the things there, and wrap up the customisation/ site editor phase.

Open floor

Collaboration with the a11yAccessibility 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) team

@annezazu shared this topic on the agenda:

Wanted to call out a great collaboration between the 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) team and core editor team in this issue: https://github.com/WordPress/gutenberg/pull/44028 It’s worth reviewing to learn from and was called out specifically by @alexstine (a11y team member) saying, “This needs to be highlighted as a good working example. It took much longer, but saves work in the future to go back and make it right.”

@jorgefilipecosta thanked @annezazu for bringing this topic to chat and thanked @alexstine for highlighting this collaboration, congratulating all the people involved in that issue.

Feedback on the Closing List view after selecting 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.

@alexstine said the following on the agenda:

This is one I could use some feedback on.
https://github.com/WordPress/gutenberg/pull/45079
This issue has been stale for some time. I am never closed to hearing other ideas, I just would really like a way forward so everyone can maximize the use of the list view since it gets more accessible every release. If my suggestion would not work for you, what would?

@jorgefilipecosta and @ndiego shared feedback/insights on the pull request.

#core-editor, #core-editor-summary, #editor, #gutenberg, #meeting, #meeting-notes, #summary

A Week in Core – October 24, 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 October 17 and October 24, 2022.

  • 49 commits
  • 75 contributors
  • 63 tickets created
  • 12 tickets reopened
  • 51 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

  • Update the Dashboard welcome banner for 6.1 – #56703

Bootstrap/Load

  • Correct sending the X-Pingback 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. in WP::send_headers()#56840

Build/Test Tools

  • Ensure PHPCSPHP Code Sniffer PHP Code Sniffer, a popular tool for analyzing code quality. The WordPress Coding Standards rely on PHPCS. related workflows are properly marked as failed – #55652
  • Hardcode the ref for the workflow dispatch on failure – #55652
  • Remove use of set-output in Action workflows – #56820
  • Update third-party welcome Action – #56793
  • Add a test case for safecss_filter_attr() with object-position property – #56793
  • Correct the wp_theme_json_data_default 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. name in assertion messages – #56796, #56835
  • Increase test coverage for WP_Theme_JSON_Resolver#56835
  • Make the message for skipping some tests with an external object cache more consistent – #56793
  • Move padding-* test data in KSES tests into its own test case – #56793

Bundled Themes

  • Twenty Twenty-Three: Sync the latest fixes for RC2 – #56383

Coding Standards

  • Use strict comparison in wp-admin/update-core.php#56866

Docs

  • Add missing default parameter value in themes_api() docblockdocblock (phpdoc, xref, inline docs)#56862, #56792
  • Add missing default parameter value in trackback_response() docblock – #56867, #56792
  • Align spelling with American English – #56811, #56792
  • Align spelling with American English – #56811, #56792
  • Document the usage of $wp_query global in WP_Media_List_Table::display_rows()#56839

Editor

  • Add font size constraints for fluid typography – #56467
  • Fix legacy group inner 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. wrappers in constrained layouts – #56467
  • Fix modal height responsiveness on link popup editor – #53174
  • Update packages for 6.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). 2 – #56467
  • Allow arrays for deprecated asset types in block registration – #56707

Embeds

  • Broaden the Tumblr oEmbed matcher to include all Tumblr URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org structures – #56733

General

  • Correctly refer to “npm” and “Node.js” – #56816

Help/About

  • Restore the correct header image for WordPress 6.1 – #56703
  • Typo correction in Dashboard Screen Options – #56884
  • Update copy & style for About page and subpages – #56357
  • Update the About header image – #56703, #56357

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.

  • Change how WP_Textdomain_Registry stores the default languages path – #39210

KSES

  • Display a notice if any of the required globals are not set – #47357

Media

  • Add object-fit to the allowed list of CSSCSS Cascading Style Sheets. properties – #56855

Networks and Sites

  • Revert the use of the metadata 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. for *_network_options functions – #56845, #37181

Query

  • Remove placeholder from query cache key. – #56802

Role/Capability

  • Revert the newly added update_role function for 6.1

Upgrade/Install

  • Add a conditional to facilitate testing of the Rollbacks feature project – #56057

Props

Thanks to the 75 people who contributed to WordPress Core on Trac last week: @xknown (10), @peterwilsoncc (9), @audrasjb (8), @SergeyBiryukov (7), @martinkrcho (6), @bernhard-reiter (5), @costdev (5), @paulkevan (5), @jrf (4), @davidbaumwald (4), @kebbet (4), @sabernhardt (4), @spacedmonkey (4), @mukesh27 (4), @dd32 (3), @richtabor (3), @johnbillion (3), @andrewserong (2), @rezakhan995 (2), @ehtis (2), @timothyblynjacobs (2), @tykoted (2), @desrosj (2), @cbravobernal (2), @voldemortensen (2), @isabel_brison (2), @pbiron (2), @ironprogrammer (2), @poena (2), @webcommsat (1), @johnjamesjacoby (1), @bph (1), @courane01 (1), @strategio (1), @rinatkhaziev (1), @dlh (1), @chaion07 (1), @dansoschin (1), @dhl (1), @talldanwp (1), @noisysocks (1), @mikachan (1), @beafialho (1), @kafleg (1), @vortfu (1), @matveb (1), @annezazu (1), @Joen (1), @rebasaurus (1), @gziolo (1), @raduiason (1), @ckanderson22 (1), @ivanjeronimo (1), @seriouslysenpai (1), @manfcarlo (1), @doctorlai (1), @pento (1), @KnowingArt_com (1), @bosconiandynamics (1), @TJNowell (1), @nendeb55 (1), @sergeybiryukov (1), @pavelschoffer (1), @flixos90 (1), @ocean90 (1), @upadalavipul (1), @saumil1611 (1), @rakibwordpress (1), @ramonopoly (1), @TobiasBg (1), @afragen (1), @ryelle (1), @adampickering (1), @mikeschroder (1), and @peterwiloncc (1).

Congrats and welcome to our 9 new contributors of the week: @rezakhan995, @raduiason, @ckanderson22, @ivanjeronimo, @seriouslysenpai, @doctorlai, @KnowingArt_com, @pavelschoffer, @saumil1611 ♥️

Core committers: @audrasjb (14), @sergeybiryukov (12), @davidbaumwald (8), @desrosj (6), @ryelle (2), @jorbin (2), @bernhard-reiter (1), @swissspidy (1), @joedolson (1), @pento (1), and @spacedmonkey (1).

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