The WordPress coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:
Found a bugbugA 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.?Create a ticket in the bug tracker.
The WordPress 6.5 retrospective survey is now closed. Thank you to everyone who responded! Expect a follow-up post with collected, anonymized results once @priethor, @marybaum, and @akshayar have finished processing all of the feedback.
GutenbergGutenbergThe 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/ 18.2 was released on April 24. Read about what’s new in this release.
We’re in the 6.6 release cycle. @annezazu shared that the roadmap draft is well underway, and @ella has already created this tracking issue to coordinate PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher backports.
@fabiankaegy noted that it is worth calling out that there are still a few roles that are looking for volunteers. @priethor added: in particular, the CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress.TriagetriageThe act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. Lead role is the one with the most in need of volunteers. There are a few inexperienced volunteers for the docs lead role, but it would be great if somebody with experience in the role could participate, too. Please reach out to @priethor directly if you have any questions.
A quick update about the next maintenance release, WP 6.5.3. There are currently 3 open trac tickets and 1 Gutenberg ticket left to resolve. A Release Candidaterelease candidateOne 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). is planned for May 2 at 17:00 UTC, with a tentative release date planned for May 7. There is more information about this release in this post, including the bugbugA 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. scrub schedule and how you can get involved.
A quick reminder that our next Gutenberg release (18.3) is in progress and the Release Candidate is scheduled for May 2.
Discussion
We dedicated the discussion time to revisiting the conversation that was kicked off last week during our announcements related to recent #core-editor conversations about how we can improve how contributors follow along with editor updates and improve communication within the project.
To kick things off, @joemcgill shared some suggestions that @youknowriad posted on the agenda:
I know a lot of Core contributorsCore ContributorsCore contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac.
https://core.trac.wordpress.org follow core updates by following the commits that happen on the #core slack channel. I believe that we should be doing the same for editor commits. These commits are already shared on slack on #core-editor-commits channel. That would be IMO a great way for core contributors to keep up with what’s happening on the editor side and potentially interact (even on merged PRs like we do for closed tickets on tracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress.) without waiting for the code to reach Core through backports or anything.
I think we can also consider showing these commits directly in the #core channel in Slack like we do for Core commits because in the end, these are core commits too, they just happen on another repository. Today we have between 10 and 20 commits per day, I think that’s an acceptable number that won’t “flood” the channel that much and would bring more visibility.
We discussed that we could experiment with posting commit summaries to the #core channel for a short period of time, such as a few weeks, and evaluate how it works. We also discussed that the commits from Core provide more detailed summaries compared to the commits to trunk on the Gutenberg repo, so this is a potential improvement for the Gutenberg commits. @audrasjb noted the Core handbook link for Commit message best practices.
@joemcgill said that he will follow up on moving this forward this week.
There was another concern in that discussion: many contributors that cannot contribute very regularly are missing when development starts for (major) new features. That results in not being able to start contributing to them in time, or not providing timely feedback, ideas, being able to test different approaches, etc. One of the ideas how to fix this was to start announcing when new major features development starts in dev. chat (and in the summaries). Seems most/nearly all contributors follow make/core and that would benefit them.
@priethor noted that Dev chat time is not very EU-friendly, asking folks to announce features here can be a big ask depending on the project.
@joemcgill summarised that there are several things to unpack here, primarily:
How can we make it easier for people to contribute to new features
What is the right timing and method for communicating updates at key milestones for a feature (e.g., merges, etc.)
@hellofromtonya suggested: How about a Make/Core post with links to tickets or project board and/or the key labels for tracking?
Open Floor
@afragen gave an update on the Merge Proposal: Rollback Auto-Update, and noted that we haven’t received any issues with testing so @afragen believes that it’s going well and we’re on our way to commit in a week or so. Also, there are 6000+ active users of the feature pluginFeature PluginA plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins. Please read the proposal and test the feature plugin in the next week, ideally before the next dev chat.
An update for the 6.6 release squad has been posted, please note that the release squad is looking for one or two CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress.TriagetriageThe act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. Leads to focus on triaging TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. and a Documentation Lead with previous experience for the role.
Also, a reminder that the WordPress 6.5 retrospective post has been published, please fill in the survey if you would like to leave feedback or suggestions for improvements to the release process. The form and comments will be open until April 26th, 2024
There was also a recent discussion in the #core-editor channel around several topics linked to how we can improve how contributors follow along with editor updates and improve communication within the project. There were several potential actions discussed, including:
Create more high-level tracking issues that are not tied to a major releasemajor releaseA 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..
Create Slack channels for high-level features, such as navigation (#feature-website-navigation) and the grid blockBlockBlock 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. (#feature-grid).
Create teams on GitHubGitHubGitHub 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 by the repository owner. https://github.com/ for high-level features to create an easy point-of-contact and discussion space for these features.
@annezazu called out that she did some recent work cleaning up the GutenbergGutenbergThe 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/ repo, which should help with this, including getting high-level overview issues in place for all phase 3 items.
@marybaum asked if we could get more support for Mission Control for this or future releases. @audrasjb has access and is willing to learn, with support from @davidbaumwald and @sergeybiryukov.
@priethor announced that WP 6.6. is not meant to be a maintenance only release. The reasons are summarized in this comment.
Next maintenance release: 6.5.3
There are currently 15 open tickets in the 6.5.3 release milestone. There is more information about this release in this post, including the bugbugA 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. scrub schedule and how you can get involved.
6.5.3 is still on target for 7 May. Scrubs have been moving things forward. There are a couple of at risk tickets so if you see something towards the bottom of https://core.trac.wordpress.org/tickets/minor/workflow, it would be good to jump in to help.
@peterwilsoncc previously raised that we should consider syncing the editor packages earlier in the release cycle. Could this be attempted for 6.6? Slack reference.
This process is documented here, but @youknowriad warned that a lot of that work is also manual for the PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher part and not something that doesn’t have a clear workflow.
@johnbillion noted a related issue, #60967, which could help with this process.
@joemcgill suggested that we put some focus on reducing friction of the PHP syncing during this release and will follow up with @youknowriad and tech leads @ellatrix, @vcanales, and @audrasjb about some next steps.
The full list of posts from the last week in Core can be read on the agenda at this link.
Open floor
There was no time for the open floor section during this dev chat, but @drivingralle did mention a potential ticketticketCreated for both bug reports and feature development on the bug tracker. for 6.6 on the agenda post:
Would be great if ticket #55184 could be included in 6.6.
“What’s new in GutenbergGutenbergThe 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 tag) are posted following every Gutenberg release on a biweekly basis, showcasing new features included in each release. As a reminder, here’s an overview of different ways to keep up with Gutenberg and the Editor project (formerly called Full Site Editing).
The latest release includes 234 pull requests from 54 contributors, and generally focuses on polishing features, and addressing bugs. Significant activity has also been directed towards improving documentation and code quality.
We extend a warm welcome and thanks to four new first-time contributors! 🎉
Gutenberg 18.2 refines the flow of turning pattern overrides on and off. It introduces a new DisallowOverridesModal for easier interaction. The solution removes complexity by focusing on a more intuitive workflow, including a modal confirmation when disallowing overrides and pre-populated names for quicker re-enablement. Through consistent interaction, we aim to simplify the user experience. (60769)
Enabling Template Preview in the Post Editor for Non-Administrators
We aim to enhance collaboration and flexibility in WordPress. By changing the rules for template previews, we now allow users with lower roles, like Editor, to view and switch between templates. This update resolves a previous issue by permitting non-administrators to see templates while editing content. (60447)
Site Editor: Support Starter Patterns
When creating a new post or page in the site editor, a modal window allows users to choose a pattern to kickstart their layout and design flow. This feature was previously only available in the post editor. (60745)
Simplify Template Reset Language
A frequent observation from previous outreach:
Why are “clear customizations” for a template in a different place (in the title area) and named differently from “reset defaults” for styles?
The term “Clear customizations” was changed to “Reset,” with label updates to maintain consistency across the Site Editor and Command Palette. This change aims to improve clarity and reduce confusion for users performing template resets. The updated terminology aligns with other languages throughout the editorial experience, making the process more intuitive. (60256)
Other Notable Highlights
Animation improvements – subtle easing can make a huge impact
Improve the headerHeaderThe 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. animation. (60408)
Editor: Animate opening and closing editor right sidebarSidebarA 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.. (60561)
Editor: Animate the inserter and list view panels. (60665)
Bump minimum required PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher version to 7.2 (60714)
Enhancements
Site Editor
Add rename and trashTrashTrash in WordPress is like the Recycle Bin on your PC or Trash in your Macintosh computer. Users with the proper permission level (administrators and editors) have the ability to delete a post, page, and/or comments. When you delete the item, it is moved to the trash folder where it will remain for 30 days. actions to page panel. (60232)
Confirm dialog: Use more descriptive text for the confirm button. (60364)
Editor: Add wordcount and reading time info in post card. (60672)
Editor: Animate opening and closing editor right sidebar. (60561)
Editor: Animate the inserter and list view panels. (60665)
Editor: Update post URLURLA specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org component. (60632)
Editor: Use the ‘ConfirmDialog’ component in template validation notice. (60385)
Enable template preview in post editor for non administrators. (60447)
Support insert before/after keyboard shortcuts when focus is within the list view. (60651)
Back Compatback compatBackward compatibility - a desire to ensure that plugins and themes do not break under new releases - is a driving philosophy of WordPress. While it is a commonly accepted software development practice to break compatibility in major releases, WordPress strives to avoid this at all costs. Any backward incompatible change is carefully considered by the entire core development team and announced, with affected plugins often contacted. It should be noted that external libraries, such as jQuery, do have backward incompatible changes between major releases, which is often going to be a greater concern for developers.: Add Patterns submenu for WordPress 6.4. (60804)
Consolidate “bound blockBlockBlock 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.” color and “synced” colors. (60617)
Improve override indication for editable blocks in synced patterns. (60599)
Refine rename flow for blocks with overrides. (60234)
Add loading state on image upload in featured imageFeatured imageA 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., Site logo and Cover blocks. (59519)
File: Use HTMLHTMLHyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers.APIAPIAn 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. to update the PDF preview label. (60494)
Navigation block: Add current-menu-item class for post type archive. (57808)
Remove block renaming control from advanced inspector controls group. (60453)
Data Views
Add ability to display fields as a badge in grid layout. (60284)
Data views table row: Make checkboxes and actions visible on touch devices. (60829)
DataViews: Make the experiment about custom views. (60813)
Layout
Add a Row control to grid layout in manual mode. (60652)
Apply negative margins for alignfull children of blocks with custom padding set. (60716)
Try reducing specificity of layout style selectors. (60228)
Include preact/debug when SCRIPT_DEBUG is enabled. (60514)
New APIs
Extensibility
Editor: Support PluginPostStatusInfo Slot in the site editor. (60814)
Editor: Unify PluginMoreMenuItem API between post and site editors. (60778)
Fix: Use coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. instead of core/editor on normalizeComplementaryAreaScope. (60821)
Fix translatable string in pagination modal. (60742)
Interactivity: Return useMemo and useCallback hooksHooksIn WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same.. (60474)
Only show block icon in toolbar for contentOnly blocks when block is a synced block. (60647)
Patterns: Guard for unknown pattern in server-side resolver. (60464)
Snackbar: Make the explicitDismiss string translatable. (60368)
Update standardisation of ‘Navigation MenuNavigation MenuA theme feature introduced with Version 3.0. WordPress includes an easy to use mechanism for giving various control options to get users to click from one place to another on a site.’ to have both words capitalised in user-facing menus. (60262)
Standardise capitalisation of Navigation Menu in sidebar. (60527)
Image: Fix cropper resize on align change (reactReactReact is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces.
https://reactjs.org-easy-crop upgrade). (60581)
Latest Posts: Remove wrapper div and apply consistent class. (60728)
Fix small regressionregressionA 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. on the resize handle. (60427)
Fix the removePropertyFromObject function throws an error if the object is null. (60831)
Router: Load proper sidebar for /wp_template. (60850)
[Site Editor]: Fix ability to edit trashed pages. (60236)
Post Editor
Editor: Do not render publish time and post status panels in design post types. (60857)
Editor: Fix post status label styles for low-capabilitycapabilityA capability is permission to perform one or more types of task. Checking if a user has a capability is performed by the current_user_can function. Each user of a WordPress site might have some permissions but not others, depending on their role. For example, users who have the Author role usually have permission to edit their own posts (the “edit_posts” capability), but not permission to edit other users’ posts (the “edit_others_posts” capability). users. (60854)
Fix display of shortcut to add non breaking space in the post editor. (60625)
Fix: Action button alignment on details panel. (60773)
Fix: Action order is different from inspector and dataviews. (60877)
Fix: Do not show pattern and template actions on the post editor. (60568)
Fix: Missing items parameter and or missing onActionPerformed calls. (60753)
Fix: Trash Post action and permanently delete post action do not show errors on single item. (60597)
Post Editor Header: Make block toolbar toggle button focus visible. (59781)
Block Editor
Avoid errors when a block variation icon is an object. (60766)
Fix external link indicator in Link Control. (60439)
Fix for isPossibleTransformForSource handling selecting inexistent block. (59410)
Fix stuck dragging mode in UI in Firefox when dealing with deeply nested lists. (60845)
Prevents delete key from undoing automatic changes. (60858)
Raw Handling – msListIgnore – Check attributes are valid. (60375)
Data Views
DataViews: Fix typing in combobox filterFilterFilters 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.. (60819)
Fix default layout configuration in pages list. (60407)
I18Ni18nInternationalization, 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.: Add context to ‘Library’ string. (60520)
Components
Fix link control link preview when it displays long URLs. (60890)
ProgressBar: Fix CSSCSSCascading Style Sheets. variable with invalidinvalidA resolution on the bug tracker (and generally common in software development, sometimes also notabug) that indicates the ticket is not a bug, is a support request, or is generally invalid. value. (60576)
Don’t output base flow and constrained layout rules on themes without theme.jsonJSONJSON, 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.. (60764)
Fix responsive column span logic on the front end. (60976)
Restore classic auto margin rule to its previous specificity. (60802)
Interactivity API
Allow multiple event handlers for the same type with data-wp-on. (60661)
Update the query block to permit non-core interactive blocks. (60006)
REST APIREST APIThe 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/
Fix PHP notice triggered by ‘gutenberg_update_initial_settings’. (60862)
AccessibilityAccessibilityAccessibility (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)
Fixes a link to the getEntityRecord documentation. (60823)
Improve documentation for block variation isActive property. (60801)
Update: Hardcoded documentation link to a branchbranchA 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". that does not exist. (60671)
Update: Reference editor scope instead of edit-site, edit-post on interface package documentation. (60818)
[Create Block] Adding documentation for the transformer property. (60445)
Tests: Shard JSJSJavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. unit tests. (60045)
Tests: Share JavaScriptJavaScriptJavaScript 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 build assets across PHP workflows. (60428)
Update: Avoid two useSelect calls on PostActions. (60752)
Update: Make content locking related selectors private. (60827)
Update: Move template actions to the editor store. (60395)
Update: Remove keyCode usage from dataviews package. (60585)
Update: Use util getVariationClassName instead of computing the variation inline. (60664)
Switching pattern categories inserter to Tabs component with arrow key navigation. (60257)
Tools
Update @talldan in codeowners file, remove from edit-widgets package. (60800)
Testing
Add end-to-end test for activating themes in site editor. (60707)
Automated Testing: Update end-to-end test npm commands. (60376)
Fix flaky Site Editor URL navigation end-to-end test. (60675)
PHP unit testunit testCode written to test a small piece of code or functionality within a larger application. Everything from themes to WordPress core have a series of unit tests. Also see regression. workflow: Try removing 7.0 and 7.1. (60686)
Perf: Improve way we measure template loading by adding posts. (60516)
Performance Tests: I’m tired of doing head math 😊. (60509)
@DaniGuardiola 🏅ProgressBar: Moved width to CSS var for performance. (60388)
@garridinsi 🏅 Interactivity API refactor to TypeScript (utils & kebabToCamelCase). (60149)
@xhemals 🏅 Update standardization of ‘Navigation Menu’ to have both words capitalized in user-facing menus. (60262), Standardise capitalization of the Navigation Menu in the sidebar. (60527)
Contributors
The following contributors merged PRs in this release:
Props to @joen, @priethor and @bphfor assisting with the preparation of this post and @vcanales, @mcsf, and @dmsnell for supporting me through my first Gutenberg release.
This post is the latest in a series of updates focused on the performance improvements of major releases (see 6.4, 6.3, and 6.2).
WordPress 6.5, “Regina” is the first major version of WordPress released in 2024. This release includes several important performance enhancements impacting the user experience for site visitors, along with remarkable improvements to editor performance. Importantly, WordPress 6.5 delivers site performance that is similar, if not superior to previous versions, despite the addition of many significant new features.
In our analysis of the Twenty Twenty-four theme, we observed modest changes in website front-end performance. The median LCP time shows a slight 0.81% decline in non-translated tests, with a 0.95% improvement in translated tests. Similarly, the Twenty Twenty-one theme exhibits a 1.13% drop in median LCP times in non-translated tests, yet showcases a notable 4.50% improvement in translated tests. Further details on the methodology behind these measurements are provided later in this article.
Key improvements
Improved performance for translated sites
This version of WordPress includes a new localization system that loads translationtranslationThe process (or result) of changing text, words, and display formatting to support another language. Also see localization, internationalization. files more quickly, and introduces support for providing translation files as native PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher files. As the merge announcement summarizes, these enhancements are expected to bring a 23.5% improvement in loading time and 41.4% reduction in memory consumption for translations.
A significantly faster editing experience
A major focus of this release was improving performance while editing your site. WordPress 6.5 delivers 5x faster typing processing, 2x faster editor loading, and a 60% reduction in pattern loading, based on measurements collected as part of the overall effort documented in this GitHub issue.
Improvements for registering blockBlockBlock 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. variations
The WordPress block editing system allows blocks to be registered with a set of block variations, which makes it easy to define different versions of a block without needing to duplicate the whole block. This version of WordPress adds support for registering block variations only when used, avoiding costly processing when this data is unnecessary, which makes server rendering 5% faster.
Support for AVIF image format
WordPress 6.5 supports AVIF, a modern image format that offers significant improvements in image quality and compression over previous formats like JPEG, PNG, and even WebP. AVIF images can be up to 50% smaller than JPEGs while maintaining the same image quality.
Additional performance focused changes
In total, there were 20 performance related improvements included in this release, split evenly between new enhancements (10) and bugbugA 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. fixes (10).
How release performance is measured
The performance measurements used for the overview are based on benchmarks1 conducted using an automated workflow on GitHubGitHubGitHub 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 by the repository owner. https://github.com/ action runners. Benchmarks were taken of the homepage of the Twenty Twenty-one, Twenty Twenty-three, and Twenty Twenty-four themes with and without translations installed, comparing WordPress 6.5 with WordPress 6.4.3 (the latest version of WP 6.4 available when 6.5 was released).
Performance metrics were collected from 100 runs for both CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Web Vitals (CWV) and Server-Timing headers provided by the Performance Lab pluginPluginA 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. using CLI scripts from the WPP Research repo.
Each release, the Performance Team looks for opportunities to improve the performance of WordPress for the following releases, which includes identifying ways we can improve the tooling and processes we use to support the performance practice. For example, we’re collecting opportunities to improve our performance testing in this GitHub issue.
You can also follow progress on other performance-related work being planned for the WordPress 6.6 release in Trac and in the Gutenberg repository. A full list of the Performance Team’s priorities for the year is available on the 2024 Roadmap page in the team’s handbook. Come join us in making WordPress as performant as possible.
Benchmark measurements use lab data to gather performance metrics under controlled conditions and may not reflect the way the software performs in the field. For more on the differences between Lab and Field data, see this article. ↩︎
TriagetriageThe act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. Leads: After some discussion and feedback, the proposal to experiment with merging the CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Triage and Edito Triage lead roles has been reverted. As a result of this, @fabiankaegy and @colorful-tones will focus on triaging the GutenbergGutenbergThe 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/ repository, and therefore, the release squad is looking for one or two Core Triage Leads to focus on triaging TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress..
Documentation Leads: In WordPress 6.5 it became clear that this role does need a bit of experience to enable the rest of the team’s contributions. Let’s ensure we find a Documentation Lead with prior experience to ensure they are able to handle release-specific work.
Default Theme Wrangler: The Default Theme Wrangler role was introduced as an experiment for 6.5 with the hopes of ensuring all default themes fully support any new features. After checking in with @poena and without any additional incoming feedback in the still-open 6.5 Release Retrospective, our recommendation is to drop the role from the squad since having the role on the squad hasn’t meaningfully impacted the default theme queue. This can be revisited in the future.
Default Theme Leads: As pointed out in the previous post comments, work towards the new default theme included in 6.7 should start during the 6.6 cycle. Even if not part of the 6.6 squad, folks interested in leading the next default theme in 6.7 are invited to express interest in the comments below. In particular, the first step to kick off the new theme would be to identify the theme designer(s).
Release squad as of April 23nd
Release LeadRelease LeadThe community member ultimately responsible for the Release.: Matt Mullenweg
The WordPress 6.5 retrospective post has been published, please fill in the survey if you would like to leave feedback or suggestions for improvements to the release process.
Forthcoming Releases
Next major releasemajor releaseA release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.: 6.6
We are currently in the WordPress 6.6 release cycle. The deadline for leaving feedback on this Planning Proposal post has ended, and we expect a release squad to be announced soon. Please leave a comment if you have any updates to share about this.
Next maintenance release: 6.5.3
WordPress 6.5.3 will be the next maintenance release. @jorbin published this post outlining the schedule.
Work on WordPress 6.5.3 is progressing. The target for release is 7 May and there are bugbugA bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. scrubs happening twice a week.
Of the tickets I’ve reviewed so far, https://core.trac.wordpress.org/ticket/60992 feels like the highest priority. It has a patchpatchA 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. on it that could use some extra testing.
@afragen confirmed that the expected behaviour of the patch for #60992 is: The patch for 60992 allows the redirect after the Activate button on the pluginPluginA 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. card in plugin-install.php. There continues to be no redirect for the Activate button in any modal, ie “More Details” or “View details” modals.
@costdev confirmed that they’re confident we can land the resolution for 6.5.3.
Next GutenbergGutenbergThe 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: 18.2
Gutenberg 18.2 is scheduled for April 24 and will include these issues.
Discussion
There were several proposed discussion topics for today:
How can we get PHP8 support completed and out of “compatible with exceptions”: suggested by @jorbin
Aligning the coding standards for CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. and Gutenberg so that both can use the same tooling: also suggested by @jorbin
Revisit syncing editor packages early and throughout the release cycle: suggested by @jeffpaul
How can we get PHP8 support completed and out of “compatible with exceptions”
On the first topic, @jorbin noted that: PHP8 support feels to me like one of those things that is kind of stagnent and I would love to see some movement towards full and complete support for all PHP8 versions. I wanted to bring it up as a topic to see if others agree or if people think the current core stance is good.
There is not currently an active effort to reach full support for PHP8.
@jeffpaul noted that: PHP Compatibility and WordPress Versions handbook page that shows PHP8 support (betaBetaA 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. support, compatible with exceptions).
@oglekler mentioned that: I am mostly working with 7.4 and from times to times have surprises like this: #46338.
@joemcgill suggested this may be a conversation that needs to start in #core-php to see if there is already an active effort in place to continue making progress, and if not, try to kickstart the process.
@jorbin noted that the outline the criteria and process for reviewing each "beta support" PHP version with each WordPress major release item is what is needed to get completed to move this forward. And then clearing out the php-compatability focus.
@joemcgill added that it seems like one of the biggest risks currently is that WP continues to show only beta support for supported PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher versions once 8.4 is released later this year, so it would be nice to make progress on this.
@costdev highlighted that this effort should be led by a sponsored contributor, due to the amount of work involved. @jorbin mentioned that if there is a host who wants to sponsor this, please get in touch via a DM or a comment on this post.
Aligning the coding standards for Core and Gutenberg so that both can use the same tooling
The lack of prettier / mismatched tooling for JSJSJavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. between the two repos
The conversation/PR a few months back to remove the WordPress-Docs ruleset from Gutenberg
It’s also something I was just raising for visibility.
It looks like @get_dave was planning on writing a Make Core post following the above discussion on GitHubGitHubGitHub 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 by the repository owner. https://github.com/. In that discussion, @antonvlasenkosummarised two issues relating to the PHP side:
Developing the missing linters to enforce WordPress Core standards.
Fixing an issue with synchronizing the rulesets between Gutenberg and WordPress to ensure a unified set of linters.
@jorbin mentioned that for the JS side, there likely is going to need to be a mass reformatting commit or two (if it’s similar to the experience from when jshint was first put into place).
Highlighted posts
The full list of posts from the last week in Core can be read on the agenda at this link.
WordPress 6.5.3 is scheduled to be the next maintenance release for the 6.5 version. Its release will follow the following preliminary schedule:
2 May 2024 – Release Candidaterelease candidateOne 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). made available and announced here on the make/coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. site.
7 May 2024 – Final release made available.
Specific times will be decided in advance and adjustments to the schedule may be made. All adjustments will be noted in this post.
Minor or Maintenance releases of WordPress are intended as bugbugA 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.-fix releases. If you have a tracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress.ticketticketCreated for both bug reports and feature development on the bug tracker. that you think should be considered, please put it in the 6.5.3 milestone. If you have a githubGitHubGitHub 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 by the repository owner. https://github.com/ issue, please add it to the 6.5.x Editor Tasks board. If you lack bug gardening capabilitiescapabilityA capability is permission to perform one or more types of task. Checking if a user has a capability is performed by the current_user_can function. Each user of a WordPress site might have some permissions but not others, depending on their role. For example, users who have the Author role usually have permission to edit their own posts (the “edit_posts” capability), but not permission to edit other users’ posts (the “edit_others_posts” capability). and have a ticket or issue you wish to highlight for 6.5.3, please add a comment here.
Note: except in extreme situations, only bug fixes will be considered and generally only bugs that have been introduced during the 6.5 cycle.
Get involved with 6.5.3
Bug Scrubs will happen in the #core room during the following times:
Each of the open tickets is going to require development work along with testing and review. You can also run your own scrubs to help ensure that all of the correct tickets are fixed in this release. Additionally, while the intent is for no new translated strings in this release, some locales have strings in 6.5 in need of translation.
General coordination for the release will happen in the #6-5-release-leads channel and decisions around code for the release will be made in the #core room.
This minor releaseMinor ReleaseA 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. will be led by @grantmkin and myself (@jorbin).
Thank you to @grantmkin for pre-publication review.
Starting Monday, April 15th 2024 at 13:00 UTC there will be a bundled theme bugbugA 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. scrub.
Currently, there are over 326 tickets in the bundled theme component queue. Recently, efforts have been made to reduce the queue, which is going well. This is part of the default theme taskforce work this year. Now is also a great time to introduce a scrub as part of that process. The following is what to expect:
An hour going through tickets one by one.
Progressing each ticketticketCreated for both bug reports and feature development on the bug tracker. raised in some way: this might be through keywords or time-framed discussions.
Congratulations to all who helped make WordPress 6.5! Now that it has launched, I invite you to reflect and share your thoughts on the release process and squad to learn, iterate, and improve for future releases.
Whether you led, contributed, tested, followed along—whatever your role, even if you didn’t have one—you are welcome to participate in this retrospective. So please take a moment to complete the form or leave public feedback in the comments below.
Please note: the survey is not anonymous. That’s in case a relevant person wants to reach you for further clarification. But your email address will not be shared publicly, and nobody is going to use it for any other purpose.
The form and comments will be open until April 26th, 2024. Shortly thereafter, you’ll see a follow-up post with collected, anonymized results.
Again, thank you for your contributions to 6.5 “Regina,” and for taking the time to help make future releases even better!
“What’s new in GutenbergGutenbergThe 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 tag) are posted following every Gutenberg release on a biweekly basis, showcasing new features included in each release. As a reminder, here’s an overview of different ways to keep up with Gutenberg and the Editor project (formerly called Full Site Editing).
With more than 150 pull requests (PRs), Gutenberg 18.1 is packed with features and bugbugA 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. fixes to suit all tastes — new pattern and template part insertion functionality, site backgrounds in global styles, accessibilityAccessibilityAccessibility (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) and performance improvements.
Lovers of documentation and code quality enhancements will be pleased to learn that their favorite PRs make up almost a third of the total number in this release!
As always, a big thank you goes out to all who contributed, with special gratitude to first-time contributors. Great work!
Version 18.1 extends background image support to top-level global styles in the Site Editor, which means you can add custom background images and photos to sites. Images can set to repeat, or be displayed as contain or cover backgrounds. (#59454)
And for those wondering — yes, as well as regular images, looping animated gifs will also work.
See more with data views
Whether it’s sorting or searching your patterns in grid and table layouts (#60337), or filtering and previewing all of your sites pages (#59950), version 18.1 brings further design consistency to configurable adminadmin(and super admin) views, not to mention quicker access and management of site assets.
Alongside the continuous integration into BlockBlockBlock 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 workflows, data views have undergone improvements to accessibility and keyboard navigation (#59637).
Pattern schema and insertion
Pattern insertion gets an upgrade in the latest version of Gutenberg. The editor canvas will zoom out when browsing and inserting patterns using the block inserter, allowing a greater overview of how your patterns appear alongside the rest of your site’s content. (#59775)
Patterns are a powerful way to define design assets with configurable content. You can now give your patterns a “schema” by naming blocks that are overridable in all instances of those patterns. Users of your patterns will be able to see exactly which blocks are editable via a handy list in the sidebarSidebarA 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.. (#59977)
Swap and edit template parts
When editing your site’s templates, you can select template parts and immediately view alternative designs for that template part in the sidebar. Want to replace your footer design? Click on your template’s footer and select a new one from the available designs. Voilà! (#60203)
Gutenberg has long had an option to preview a page’s template when editing that page. 18.1 lets you select and edit a page’s important template parts, such as the headerHeaderThe 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. and footer. To do so, click on a template part, then hit “Edit” in the toolbar. (#60010)
Other notable highlights
The editor displays a confirmation modal before clearing template customizations. (#60119)
You can collapse non-selected items in the list view using a handy new keyboard shortcut (Option-L on Mac, or Alt-L on Windows). (#59978).
Changelog
View the full changelog
Enhancements
Block Editor
Zoom out: Invoke zoom out mode when opening the patterns tab, and move the code to do so to a shared hook. (59775)
Block Previews: Update shadows in different contexts. (60161)
Update: Move post actions to the editor package. (60092)
Consolidate when showing revisionsRevisionsThe 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. link or action. (60194)
Editor: Update hover color of editor document title. (60113)
Add content schema to pattern editing view. (59977)
Close inspector on pattern categoryCategoryThe 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. select. (60004)
Focus block selection button only in navigation mode. (60207)
Pattern Shuffling: Make the results deterministic. (60074)
Add __next40pxDefaultSize to Image block Title Attribute. (60117)
Add support “HTMLHTMLHyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. Element” to Site Tagline. (59654)
Image: Remove temporary image check for rendering controls. (60212)
Reduce specificity of block library styles conflicting with block supports. (59457)
Update navigation blocks to use consistent link UIUIUser interface labels and field sizes. (60116)
Summary: Polish featured imageFeatured imageA 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.. (60110)
Data views: Add confirmation modal for clearing customizations in templates. (60119)
Data views: Make trashTrashTrash in WordPress is like the Recycle Bin on your PC or Trash in your Macintosh computer. Users with the proper permission level (administrators and editors) have the ability to delete a post, page, and/or comments. When you delete the item, it is moved to the trash folder where it will remain for 30 days. a quick action again. (60165)
List View
Add keyboard shortcut to collapse list view items other than the focused item. (59978)
Adjust the List View close icon to resemble the Inspector close icon. (59999)
Update “Actions” string to “Options” in List View. (60136)
Templates
Add filterFilterFilters 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. to allow extending the list of post content blocks. (60068)
Render non-editable preview of template part when user does not have capabilitycapabilityA capability is permission to perform one or more types of task. Checking if a user has a capability is performed by the current_user_can function. Each user of a WordPress site might have some permissions but not others, depending on their role. For example, users who have the Author role usually have permission to edit their own posts (the “edit_posts” capability), but not permission to edit other users’ posts (the “edit_others_posts” capability). to edit template part. (60326)
Template Parts: Remove pattern title from sidebar. (60160)
Template Parts: Update replace flow to separate template parts from patterns. (60203)
Template Parts: Update the ‘Replace’ label to ‘Design’. (60156)
Zoom Out
Add a delete control to toolbar on zoomed out mode. (60214)
Media dialog push content in zoomed out mode. (60170)
Components
Popover / ToggleGroupControl: Use useReducedMotion() from @wordpress/compose. (60168)
REST APIREST APIThe 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/
Allow view access of template rest endpoint to anyone with the edit_post capability. (60317)
Site Editor: Consolidate save button functionality. (60077)
Revert #60300: Make sure the CSSCSSCascading Style Sheets. class id-dark-theme is added to the editor iframeiframeiFrame is an acronym for an inline frame. An iFrame is used inside a webpage to load another HTML document and render it. This HTML document may also contain JavaScript and/or CSS which is loaded at the time when iframe tag is parsed by the user’s browser. body. (60616)
Block Editor
Make sure the CSS class is-dark-theme is added to the editor iframe body. (60300)
BackportbackportA 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.r57868 (Editor: Prevent font folder naive filtering causing infinite loops) from WordPress-Develop. (60141)
Block templates
Add null check to prevent errors in get_block_template filter. (60491)
Utilities
URLURLA specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org: Return early in getFilename where URL argument is falsy. (60265)
Accessibility
Data Views
Add click-to-select behavior on table rows. (59803)
Data views list layout: Apply focus styles to items on focus-visible rather than focus. (60253)
Add auto generated APIAPIAn 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. documentation for editor package. (60356)
Fix @todo tags to follow standards in WordPress comments. (60148)
Fix Font Collection JSONJSONJSON, 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. schema definition. (60285)
Fix: InvalidinvalidA resolution on the bug tracker (and generally common in software development, sometimes also notabug) that indicates the ticket is not a bug, is a support request, or is generally invalid. documentation link to load JavaScriptJavaScriptJavaScript 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. (60181)
Fix: Invalid links to the block supports api. (60199)
Fix: Non existent link to submitting to the block directory. (60389)
Interactivity API: Variable name correction in the documentation. (60056)
Create Block: Update external template documentation to include variants. (60095)
Update: Use getPostIcon selector on document bar. (60128)
Distraction free: Remove unwanted space from string. (60108)
Global Styles
Additional CSS: Add code comments contextualising tranformStyles for clarity. (60267)
Global styles: output :root selector for CSS custom properties. (42084)
Style Engine: Continue get_classnames loopLoopThe 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 after adding the default classname. (60153)
Font Library
Add test for Font Library and Theme Style Variations. (60250)
Update google fonts font collection data URL to the latest version available. (60079)
Block Library
Image: Use the new ‘useUploadMediaFromBlobURL’ hook. (60208)
Navigation Block: Add test coverage to check that post content is not removed. (60189)
Site Editor
DataViews: Don’t memoize every callback ‘PagePages’ component. (60103)
History: Simplify the push and replace methods. (60112)
Rich Text
RichText: Separate fallback instance ID for selection retrieval. (60277)
Block Locking
E2E: Test BlockSwitcher availability in l-post-ul-group CPT. (60254)
Data Views
DataViews: Fix reactReactReact is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces.
https://reactjs.org warning error in list layout. (60101)
Tools
Testing
Automated Testing: Remove Puppeteer CI Job. (59311)
Blocks: Fix double gutenberg_ prefix in built dynamic blocks PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher. (60288)
First-time contributors
The following PRs were merged by first-time contributors 🎉 :
@interdevel: Fix @todo tags to follow standards in WordPress comments. (60148)
You must be logged in to post a comment.