Category Archives: General

Aaron Jorbin 9:28 pm on January 20, 2026
Tags: , , 6-9-x,   

WordPress 6.9.1 Release Schedule

Since WordPress 6.9 was released, contributors have kept a close eye on incoming reports to the WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ Support Forums, TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., and the GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ repository on GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. https://github.com/. The volume and severityseverity The seriousness of the ticket in the eyes of the reporter. Generally, severity is a judgment of how bad a bug is, while priority is its relationship to other bugs. of tickets mean that the maintenance release should be prepared sagaciously.

This release will be co-led by @jorbin and @wildworks.

Schedule

Date/TimeEvent
Tuesday, January 20, 2026 at 22:00 UTCBug Scrub
Thursday, January 22, 2026 at 09:00 UTCBug Scrub
Thursday, January 22, 2026 at 16:00 UTCBug Scrub. WordPress 6.9.2 Milestone will be opened, and some tickets may be punted.
Tuesday, January 27, 2026 at 09:00 UTCBug Scrub
Tuesday, January 27, 2026 at 18:00 UTCBug Scrub.
Thursday, January 29, 2026 at TBA UTCWordPress 6.9.1 RC1
Tuesday, February 3, 2026WordPress 6.9.1 General Release

Specific times for 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). and General release will be announced in the 6.9 Release Leads room and will be based on availability of individuals helping with the release.

Targeted Fixes

WordPress 6.9.1 is intended as a 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.-fix only maintenance release. Tickets will be included provided they are issues introduced during the 6.9 cycle or intentionally deferred at the end of the 6.9 cycle. You can follow trac report 4 or the 6.9.x editor tasks board for proposed fixes.

Some issues already have hotfixes available in plugin form if you are facing them on your site.

Get Involved with 6.9.1

Bug Scrubs will happen in the #core room during the times posted above. 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, some locales have strings in 6.9 in need of translation.

General coordination for the release will happen in the #6-9-release-leads channel and decisions around code for the release will be made in the #core room.

Props to @wildworks, @dmsnell, @westonruter for assistance with this post.

#6-9, #6-9-1, #6-9-x, #minor-releases

Benjamin Zekavica 11:45 am on January 15, 2026
Tags: , ,   

Summary, Dev Chat, January 14, 2026

Start of the meeting 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/, facilitated by @desrosj 🔗 Agenda post.

Announcements 📢

WordPress 7.0 Call for Volunteers

If you are interested in volunteering for WordPress 7.0, please comment here by January 16.

Nominations for CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Team Reps 2026

The nomination process for Core Team Representatives for 2026 is now open. Please submit your nomination here.

Dropping support for PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher 7.2 and 7.3

Support for PHP 7.2 and 7.3 will be dropped in WordPress 7.0. Here you can find more information.

6.9 Release Retrospective

The 6.9 release retrospective is open to all contributors, not only release squad members.
Broader feedback helps improve future release processes. The form and comments will be open until January 15.

Discussions 💬

PHP Extensions List – filter

The topic was about the PHP filter extension and if it should be default. It was noted that the extension already exists on almost all PHP installs. The idea was to move it from optional to built-in (default), so no extra checks are needed. It was also noted that WordPress Core barely uses it, except in PHPMailer, and that filter functions, especially for email checks, are not very reliable.

#7-0, #core, #dev-chat

Jonathan Desrosiers 1:19 am on January 9, 2026
Tags:   

WordPress 7.0 Call for Volunteers

Planning is underway for WordPress 7.0! This post outlines the proposed schedule along with a call for volunteers to support the release process.

Following the typical cadence and accounting for holidays later in the year, the proposed final release date for 7.0 is Thursday, April 9, 2026. This proposed timeline remains flexible for the resulting Release Squad and adjustments can be made if necessary as they determine what timeline works best for their schedule.

Proposed Schedule

MilestoneDate
Alpha BeginsImmediately (7.0-alpha began in trunk on November 12th with [61222])
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. 1Thursday, February 19
Beta 2Thursday, February 26
Beta 3Thursday, March 5
Beta 4Thursday, March 12
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). 1Thursday, March 19
Release Candidate 2Thursday, March 26
Release Candidate 3Thursday, April 2
Dry RunWednesday, April 8
Final ReleaseThursday, April 9

As always, all dates are subject to change based on development progress.

Call for Volunteers

Each WordPress release depends on contributors from across the project coming together to make it a success. 

As with the 6.7, 6.8, and 6.9 release cycles, WordPress 7.0 will continue the approach of forming a smaller, focused Release Squad with making based on feedback received. This streamlined structure places more emphasis on collaboration with the various Make Team Reps, who are encouraged to help coordinate efforts from within their respective teams. The goals are to reduce the overhead on the Release Squad while still ensuring each team’s contributions and priorities are represented throughout the cycle, and to reduce overlap between a Make Team RepTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. and that team’s Release Squad Leads. Noteworthy Contributors will be captured from Team Reps towards the end of the release cycle.

While the end goal is to publish the final release of WordPress 7.0 during Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/ at WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Asia (which follows India Standard Time), traveling to or attending WordCamp Asia is not a requirement to serve on the release squad. All communication related to the release process will continue to take place in the #core 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/ channel.

If you are interested in helping lead WordPress 7.0 in one of the following roles, please comment below or reach out in the #7-0-release-leads Slack channel:

  • Release LeadRelease Lead The community member ultimately responsible for the Release. – Matt Mullenweg (@matt)
  • Release Coordination – helps manage timelines, cross-team collaboration, and status updates
  • Tech Leads – oversees coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development (including 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/), triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors., and critical issues
  • Triage Lead – help monitor issues, shepherd patches, and guide contributors
  • Test Lead – coordinates testing efforts across the community and test reports

Whether you have led a release before or are looking to get involved for the first time, there are many ways to contribute. Volunteers of all backgrounds and experience levels are welcome!

If you are interested in volunteering, please leave a comment below noting your preferred area(s) by Friday, January 16th. @4thhubbard (or a designee), will review the nominations shortly after to confirm and announce the release squad as soon as possible.

Together we can make WordPress 7.0 the best one yet!

Props to @jeffpaul, @jorbin, and @4thhubbard for reviewing this post.

#7-0

Benjamin Zekavica 4:38 pm on January 7, 2026
Tags: , ,   

Summary, Dev Chat, January 7, 2026

Start of the meeting 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/, facilitated by @benjamin_zekavica 🔗 Agenda post.

Announcements 📢

6.9 Release Retrospective

The 6.9 release retrospective is open to all contributors, not only release squad members.
Broader feedback helps improve future release processes.

Discussions 💬

PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher Extensions List – filter

The discussion covered whether the PHP filter extension is set as default. See the Hosting Team Handbook. @dmsnell asked about the impact on CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., how similar changes were handled before, and mentioned concerns about using functions like FILTER_VALIDATE_EMAIL. @realloc noted that Core uses filter only in a few places, mainly in PHPMailer, and suggested removing those usages instead of requiring the extension. The topic will be discussed again next week.

#7-0, #core, #dev-chat

Akshaya Rane 2:12 pm on December 19, 2025
Tags: , ,   

WordPress 6.9 Release Retrospective

Congratulations to all who helped make WordPress 6.9 possible!

Now that the release cycle is complete, you’re invited to reflect and share your thoughts on the release cycle, release processes, release squad, or whatever else is on your mind. Feedback loops are critical to learning what works and what doesn’t so that the teams involved can iterate on the processes to improve for future releases. 

Everyone is welcome to submit feedback about the release using this form, even contributors who did not contribute directly to the release itself.

A member of the community that casually observes a release cycle will have very different thoughts and opinions than someone who was heavily involved on a weekly or daily basis. The more viewpoints and backgrounds represented within this feedback loopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop the better. So please take a moment to complete the form or leave public feedback in the comments below.

Please note: the survey is not anonymous, but anything submitted will be anonymized before being shared in a post summarizing the results. Your wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ username is required just case the person processing the responses needs to reach out to you for further clarification.

The form and comments will be open until January 15, 2026. A follow-up post with the collected, anonymized results will be published shortly after.

Again, thank you for your contributions to 6.9 “Gene,” and for taking the time to provide valuable feedback to help make future releases even better!

Props to @amykamala, @desrosj for the peer review.

#6-9, #release-process, #retrospective

Héctor Prieto 9:32 pm on December 17, 2025
Tags:   

Gutenberg 22.3 (December 17)

“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, 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.

What’s New In
Gutenberg 22.3?

Gutenberg 22.3 is here and ready for download!

This release brings a dedicated Fonts page for easier typography management, responsive Grid layouts, continued progress on the Site Editor’s routing infrastructure, and improvements to the image editing experience.

Dedicated Fonts page for easier typography management

A dedicated Fonts page is now available under the Appearance menu for 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. themes. Until now, font management has lived deep inside Global Styles, requiring navigation through several panels to install or preview a font. This new standalone page lets block theme users browse, install, and manage their typography collection in one dedicated space. Support for non-block themes will come next.

Under the hood, this page is built on a new routing infrastructure for the Site Editor, designed to improve navigation and support new top-level pages in wp-adminadmin (and super admin). View transitions are now wired into this routing layer, providing early zoom/slide animations when navigating between pages.

Image editing improvements

The in-editor image cropper has been rebuilt on a new foundation. While the workflow remains familiar, you’ll notice improvements: aspect ratios and zoom levels now persist when rotating images, fixing a long-standing frustration. This refactor also lays the groundwork for future image-editing enhancements. (#72414, #73277)

Responsive Grid block

The Grid block now adapts to different screen sizes when columns are set. Layouts will adjust naturally across devices, providing a more consistent experience for visitors on mobile and desktop alike.

Other highlights

A few more highlights worth mentioning:

Changelog

Enhancements

Block Editor

  • Image Cropper: Add package and basic stories. (72414)
  • Implements the image-cropper package in the editor. (73277)

Block Library

  • Add support for ‘align’ to the Breadcrumbs block. (73794)
  • Breadcrumbs: Support paged comments. (73670)
  • Button: Migrate to text-align block support. (73732)
  • Comments Pagination Numbers: Add spacing controls for margin and padding. (67267)

Components

  • Chore: Shorten timeout duration for Snackbar component. (73814)
  • Try: 32px tall menu items. (73429)

Data Layer

  • wordpress/data: Migrate index.js to index.ts. (73597)

DataViews

  • Add min/max validation support to DataForm inputs. (73465)
  • Field 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.: Display formats for number and integer types. (73644)
  • Try using 24px padding for consistency across different uses. (73334)
  • Update operator labels and deprecate the isNotAll. (73671)

Internationalization

  • Fields: Update “TrashTrash Trash 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.” translationtranslation The process (or result) of changing text, words, and display formatting to support another language. Also see localization, internationalization. to provide verb context. (73704)

Layout

  • Enable grid block to be responsive when columns are set. (73662)
  • Try removing top and left grid drag handles in stable (auto) mode. (73864)

Media

  • Add media-specific fields for use with Attachment post types and DataViews/DataForm. (73071)

Notes

  • Notes: Add email notification. (73645)

Offline

  • Editor: Improve offline error notices. (73874)

Packages

  • Remove WordPress dependencies from abilities package. (73428)

Patterns

  • Add pattern name to document toolbar when editing in spotlight. (73208)
  • ContentOnly: For template parts and synced patterns, ensure ‘Edit section’ button goes to the isolated editor. (73736)

Post Editor

  • Use relevance pattern matching for parent page search. (73836)

Site Editor

  • Site Editor Pages: Add “notes count” field. (73609)

Theme

  • Expand error family of tokens. (73793)

Bug Fixes

Block API

  • Fallback to all attributes when checking for unmodified block. (73867)

Block Editor

  • Link Control: Clear entity metadata when selecting custom URLs. (73825)
  • Block Styles: Fix dynamic block previews. (73709)
  • Pattern insertion: Drag chip when multiple blocks of the same type in a pattern are dragged. (73681)

Block Library

  • Accordion Heading: Add default style for classic themes. (73608)
  • Add 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. support for math block error messages. (73643)
  • Breadcrumbs: Improve home page and front page handling. (73487)
  • Classic Block: Restore HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. editing option. (73865)
  • Fix Page List block HTML rendering in editor. (73614)
  • Fix Page List block button HTML rendering to escape at output. (73641)
  • Fix align right issue on avatarAvatar An avatar is an image or illustration that specifically refers to a character that represents an online user. It’s usually a square box that appears next to the user’s name. component. (67494)
  • Post Title: Add fallback no title in edit mode when is readOnly. (73750)
  • Post Title: Fix empty heading element when post_title is empty but get_the_title returns markup V2. (73841)
  • Prevent flipping the border style when creating RTL stylesheets. (44170)
  • Verse Block: Prevent text overflow off-screen when the previous block has float. (45221)

Block Transforms

  • Gallery: Fix missing captions shortcodeShortcode A shortcode is a placeholder used within a WordPress post, page, or widget to insert a form or function generated by a plugin in a specific location on your site. transform. (73748)

Command Palette

  • Commands: Restrict editor UIUI User interface commands to entity-edit context. (73717)
  • Fix layout for long label. (73837)
  • Remove context from editor commands. (73807)

Components

  • Fix Notice component action button margins. (69430)
  • Reduce modal style specificity so it can be overridden more easily. (73739)

DataViews

  • Apply primary style to first column if there is no title field. (73729)
  • Fields: Fix suffix button in Slug field. (73829)
  • Fix sticky footer in dataviews grid view. (73661)

Font Library

  • Fix button background and focus outline styles. (73722)

Global Styles

  • Fix: Default color variations not showing in global styles. (73742)
  • Global Styles UI: Remove unnecessary padding for Navigatior component. (73810)
  • Global Styles UI: Restore borders for preview items. (73741)
  • Global Styles UI: Revert some of the padding / markup changes from #73334. (73834)
  • 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.: Override coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. classic theme styles. (73580)

Inspector Controls

  • Fix Hstack prop in PostCardPanel. (73842)

Notes

  • Notes: Avoid incrementing comment_count when notes are resolved or reopened. (73689)
  • Notes: Ensure notes never show on the comments page. (73640)

Paste

  • Raw Handling: Fix grok markdown pasting issues. (73019)

Patterns

  • contentOnly patterns: Mark patterns as contentOnly by adding metadata.patternName to the root block. (73477)

Templates API

  • Template Activation: Update template ID format test. (73629)

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)

Block Editor

  • Fix block toolbar icon CSSCSS Cascading Style Sheets. when using show icon label preference. (73674)

Performance

Block Editor

  • Block Styles: Avoid re-rendering when typing. (73701)

Theme

  • Theme: Better max chroma detection for taperChroma. (73625)

Experiments

Block API

  • PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher-only blocks: Pass all metadata from PHP registration to the client. (73556)

Collaboration

  • Real-time collaboration: Add UndoManager support for collaborative editing. (72407)
  • Real-time collaboration: Disable syncing for “synthetic” template posts. (73526)

Font Library

  • Add dedicated font library page. (73630)
  • Add Overlay template part area behind Experiment. (73359)
  • Add overlay template part selector to Navigation block (behind experiment). (73760)

Routing

  • Boot: Add conditional inspector rendering via route.inspector(). (73703)
  • Routing Boot package: Add mobile rendering. (73620)
  • Routing: Add page title support. (73847)
  • Routing: Add view transitions to the new routing infrastructure. (73586)

UI Components

  • UI: Add border support to Box component. (73530)
  • UI: Add Stack component leveraging gap spacing design tokens. (73308)
  • UI: Update Stack component to support only gap tokens. (73852)

Documentation

Block API

  • Block 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. schema: Add visibility key to supports definition. (73612)
  • Docs: Add “Migrating Blocks for iframeiframe iFrame 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. Editor Compatibility” page. (73778)
  • Docs: Add missing periods to example descriptions in block-attributes.md. (73666)
  • Update Default block example code. (65229)

Components

  • Docs: Add JSDoc for getUserLabel in users autocompleter. (73651)

DataViews

  • DataViews docs: Add missing props. (73611)
  • DataViews stories: Update empty story. (73619)

General

  • Fix a typo in the documentation. (73658)

Packages

  • Docs: Update package documentation with general guidelines. (73633)

Storybook

  • Storybook: Add keywords to icon stories. (73524)

Code Quality

Block bindings

  • Block Bindings: Componentize. (73579)

Block Editor

  • Fix ESLint warnings for the ‘useInsertionPoint’ hook. (73868)
  • Fix block edit component hook dependencies. (73302)
  • Remove unused ‘__unstableBlockNameContext’. (73783)
  • Remove usage of Emotion. (73799)
  • Simplify ‘useSelect’ deps in ‘InserterDraggableBlocks’. (73687)

Collaboration

  • Notes: Simplify editing mode change position tracking. (73696)

Components

  • AlignmentMatrixControl: Fixup style names and nesting. (73757)
  • AlignmentMatrixControl: Migrate Emotion to style.module. (73714)
  • AnglePickerColor: Migrate Emotion to style.module. (73786)
  • FormTokenField, FlatTermSelector: Hard deprecate bottom margin. (73846)

DataViews

  • Field API: Move validation to the field type. (73642)
  • Remove extra wrapper for GridItem. (73665)

Font Library

  • Move Font Collection fetching to core-data entities. (73635)
  • Move font family fetching and types to core-data. (73637)
  • Simplify cache invalidation. (73639)

Global Styles

  • Fix ‘useSelect’ warning. (73728)
  • Fix browser warnings in Global Styles. (73279)
  • WP_Theme_JSON: use self:: For class private static methods. (73566)

Patterns

  • ContentOnlyControls: Refactor ad hoc fields to use setValue instead of updateBlockAttributes. (73680)

Site Editor

  • Fix ‘useNavigateToPreviousEntityRecord’ internal deps. (73740)

Style Book

  • Fix ESLint warnings. (73882)

Theme

  • Theme: Repurpose Figma token plugin to extract JSON override files for modes. (73860)
  • Theme: Restructure theme tokens to embed prefix, flattened modifiers. (73859)
  • Theme: Use valid DTCG color format for primitive values. (73858)

Write mode

  • Block Editor: Restore ToolSelector component for backward compatibility. (73592)

Tools

Build Tooling

  • Attachments controller: Use 6.7 compat method. (73634)
  • Fix package side effects for esbuild. (73795)
  • Linting: Disable the wordpress dependency group lint rule. (73616)
  • MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress.: Add Carlos Bravo to mailmap. (73840)
  • Meta: Introduce .mailmap for transforming author names. (72412)
  • Scripts: Update license checker to ignore invalidinvalid A resolution on the bug tracker (and generally common in software development, sometimes also notabug) that indicates the ticket is not a bug, is a support request, or is generally invalid. package entries. (73528)
  • Storybook: Skip transpilation of build-modules files. (73780)
  • wp-build: Fix invalid package references for peer dependencies. (73676)
  • wp-ui: Add legacy export fields to package.json. (73850)
  • Fix CI static analysis on Windows. (73911)

Testing

  • Remove custom import resolvers and package subpath syntax rules. (72978)
  • Tests: Emulate form blocks experiments in integration tests. (73705)
  • Tests: Update assertion for ‘Global styles 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.’ end-to-end test. (73685)
  • Upgrade Playwright to v1.57. (73686)

Patterns

  • Content only and patterns: Detach edit fields from the content only experience. (73605)

First-time contributors

The following PRs were merged by first-time contributors:

  • @badasswp: Chore: Shorten timeout duration for Snackbar component. (73814)
  • @dhasilva: DataViews: Apply primary style to first column if there is no title field. (73729)
  • @manhphuc: Docs: Add missing periods to example descriptions in block-attributes.md. (73666)
  • @metodiew: Fix a typo in the documentation. (73658)

Contributors

The following contributors merged PRs in this release:

@aduth @Aljullu @andrewserong @annezazu @badasswp @cbravobernal @chriszarate @dhasilva @dmsnell @getdave @gigitux @huzaifaalmesbah @Infinite-Null @ingeniumed @jameskoster @jasmussen @jeryj @jonathanbossenger @jorgefilipecosta @jsnajdr @juanfra @lezama @Mamaduka @manhphuc @Mayank-Tripathi32 @metodiew @mikachan @mirka @ntsekouras @oandregal @ockham @priethor @ramonjd @ryelle @scruffian @shimotmk @SirLouen @t-hamano @tellthemachines @tyxla @Utsav-Ladani @yogeshbhutkar @youknowriad

Props to @youknowriad for the peer review.

Benjamin Zekavica 8:59 pm on December 17, 2025
Tags: , ,   

Summary, Dev Chat, December 17, 2025

Start of the meeting 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/, facilitated by @desrosj 🔗 Agenda post.


Note: This was the final Dev Chat of 2025. The next Dev Chat will take place on January 7, 2026. Bug scrub meetings may still take place in the meantime. Thanks everyone, and see you in the new year.

Announcements 📢

GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ 22.3 has been released!

Gutenberg 22.3 is now available for download!

WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Asia 2026 Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/: Call for table leads

Contributors interested in helping with the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Team during the WordCamp Asia 2026 Contributor Day can contact @krupajnanda.

WordPress 6.9 Hotfixes

Since the WordPress 6.9 release, several issues have been reported, temporary workarounds are available as plugins and will be included in a maintenance release planned for January 2026 at the earliest, with full details in the linked post.

Planning for WordPress 7.0

With 6.9 released, attention is already shifting toward WordPress 7.0, including early ideas, focus areas, and ways to contribute, all outlined in the follow-up post.

Real-time collaboration: Early user feedback

Real-time collaboration for WordPress 7.0 has been in WordPress VIP 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. testing since October 2025, with early feedback covered in this post.

Discussions 💬

Dev Chats Over the Holidays

During today’s meeting, it was decided to skip the next two Dev Chat meetings, making today’s meeting the final Dev Chat of the year. Bug scrub meetings may still take place during this time. The next Dev Chat is scheduled for January 7, 2026.

#7-0, #core, #dev-chat

Aaron Jorbin 7:22 pm on December 12, 2025
Tags:   

WordPress 6.9 Hotfixes

Since being released on December 2, WordPress 6.9 has been downloaded over nine million times. Shipping is the first step, and core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org have been monitoring 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, forum posts, and social networks to see the effects of the release. Issues are analyzed to understand how widespread they are, the impact they have on sites, and if there is a viable workaround available. This is combined with analyzing potential release dates, coordination with other projects that may be necessary, and the riskiness of fixes to decide on a release date for a maintenance release. Please note, only a small subset of sites are facing these issues.

For WordPress 6.9, this analysis has led to the decision that a maintenance release will be best in January at the earliest.

Some of the reported bugs can be fixed using small code snippets, but not everyone is comfortable editing PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher files on their site. To reduce the burden on site administrators who are affected by these reported bugs, these snippets have also been made available as plugins. It is recommended to test your site before installing one of these plugins.

CSSCSS Cascading Style Sheets. Issues from Loading Separate BlockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. Styles on Demand

WordPress 6.9’s new ability to load block styles on demand in classic themes has led to some instances where some sites running a classic theme are seeing content styled in unexpected ways due to wp-block-library styles being omitted when they were previously included by default. There can also be differences in file loading leading to unexpected changes in the CSS Cascade. See #64354 for more information and to follow as a permanent fix is developed.

The Load Combined Core Block Assets Plugin by coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. committercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component. @westonruter is available to help here.

E-Mails Not Being Sent

Some changes aimed at improving the reliability of email have uncovered bugs with some configurations of the underlying libraries and applications used to send email. This means that is some circumstances, WordPress installs that had been able to send emails no longer can. See #64368 for more information and to follow as a permanent fix is developed.

The Hotfix 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., maintained by multiple core committers, has been updated to include a workaround.

Adjacent Post Navigation

Additionally, a change to adjacent post navigation is leading to some sites seeing infinite loops when modifying the get_{$adjacent}_post_where 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.. This change was not previously publicized, but the linked dev notedev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. is now published and highlighted in the 6.9 field guide. Please ensure you are using the most up-to-date version of plugins and themes when updating to WordPress 6.9.

Thank you to the contributors who have tested and reported issues they have seen along. Futher, thank you to the developers who have followed up on these reports and are continuing to work to find solutions that help WordPress users in both the short and long term. As a community project, WordPress would not be able to function without the volunteers and individuals sponsored to work on WordPress Core. If you see an issue, please report it to either trac or the gutenberg repository depending on where the issue occurs.

Props @desrosj and @westonruter for assisting with drafting this post.

#6-9

Benjamin Zekavica 4:57 pm on December 10, 2025
Tags: , ,   

Summary, Dev Chat, December 10, 2025

Start of the meeting 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/, facilitated by @benjamin_zekavica 🔗 Agenda post.

Announcements 📢

WordPress 6.9 is now available!

WordPress 6.9 is now available for download. Huge thanks to all contributors who made this release possible. 

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/ 22.2 has been released!

Gutenberg 22.2 has been released and is available for download!

Discussions 💬

6.9.1 Planning

A review of the tickets reported since the 6.9 release does not indicate a need for an immediate 6.9.1 maintenance release. The feedback so far does not point to issues that require a rapid response. A timeframe early in the new year is being considered to allow enough time for further testing and coordination. @jorbin will prepare a post for the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. blogblog (versus network, site) to share the current status.

Missing “Needs Patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. / Needs PR” Label in the Gutenberg Repository

@sirlouen raised that it is often unclear when a Gutenberg issue is ready for patch work. Some issues may appear complete, even though they still require review or testing. The current labels do not always show this distinction, which can make it harder to identify issues that are ready to work on. It was also noted that clearer information about the issue workflow could help improve orientation.

#6-9, #core, #dev-chat

Rodrigo Primo 11:22 am on December 5, 2025
Tags: , ,   

Coding Standard Proposal: Allow the use of the PHP short echo tag

Currently, the WordPress Coding Standard explicitly forbids the use of the PHP short echo tag (<?=) along with the PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher short 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.) (<?). This post proposes modifying this rule to allow the use of the short echo tag for single statements.

Motivation

Prior to PHP 5.4, it was possible to disable the PHP short echo tag (<?=) using the PHP short_open_tag ini directive. This meant that scripts using this tag could not be used in code that must work across different PHP installations, because the content within those tags may be printed instead of executed, which could lead to code exposure. For this reason, the WordPress Coding StandardsWordPress Coding Standards The Accessibility, PHP, JavaScript, CSS, HTML, etc. coding standards as published in the WordPress Coding Standards Handbook. May also refer to The collection of PHP_CodeSniffer rules (sniffs) used to format and validate PHP code developed for WordPress according to the PHP coding standards. forbid its use.

Since PHP 5.4, the short echo tag is always available, and changing the short_open_tag directive no longer affects it. WordPress dropped support for versions prior to PHP 5.6 in 2019, and since then raised the minimum supported PHP version to 7.2. Currently, according to WordPress.org stats, the percentage of active WP installs using PHP < 5.4 is 0.4% and the percentage of sites still using WP < 5.2 is 4.0%. Therefore, it is now safe to allow the use of short echo tags.

This tag is useful as it provides a more concise syntax for outputting values in template files. WordPress developers should be allowed to use it. An issue requesting this change is the most liked issue in the WPCSWordPress Community Support A public benefit corporation and a subsidiary of the WordPress Foundation, established in 2016. repository, indicating community support.

This proposal is about allowing the use of the short echo tag for single statements, not encouraging its use, so no immediate changes are required. In practice, this means that:

  • Existing open patches for CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. are not affected as either style is allowed.
  • Existing WP Core code and code in official WP themes should not be updated, as both styles are permitted. A patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. to enforce the use of short echo tags in all possible places will NOT be accepted.
  • However, a new official theme could choose to use short echo tags if desired.

Suggested change to the handbook

The suggestion is to modify the rule titled “No Shorthand PHP Tags” as follows:

New title: No PHP short open tag

Content:

Important: Never use the PHP short open tag (`<?`). Always use the full PHP open tag (`<?php`). Using the PHP short echo tag (`<?=`) is allowed, though short echo tag snippets should only contain a single statement.

Correct:

<?php … ?>
<?= esc_html( $var ); ?>

Incorrect:

<? … ?>

How to keep short echo tags forbidden in a given project

If this proposal is accepted, but a project wants to keep the short echo tag forbidden in its own codebase, it can do so by adding the following snippet to its PHPCSPHP Code Sniffer PHP Code Sniffer, a popular tool for analyzing code quality. The WordPress Coding Standards rely on PHPCS. configuration after the WordPress standard is included:

<rule ref="Generic.PHP.DisallowShortOpenTag.EchoFound">
    <severity>5</severity>
</rule>

References

#codingstandards, #php, #wpcs

Props @dingo_d, @garyj, and @jrf for reviewing this post.