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.8.2 is now available! The release proceeded as planned, resolving 20 TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets and 15 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/ pull requests. CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. releases 4.1 to 4.6 were also completed successfully, with the exception of 4.6, which encountered a build error in Mission Control. The issue is currently under review. Additional releases for older branches are planned to update certificates (see TicketticketCreated for both bug reports and feature development on the bug tracker.#63165).
WordPress 6.9 Planning Proposal and Call for Volunteers
WordPress 6.9 is scheduled on Tuesday, December 2, 2025.
Discussion 💬
Refactoring wp_kses_hair()
#63694: Discussion focused on replacing wp_kses_hair() with the 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 improve parsing reliability. Part of the change includes switching tests from assertSame() to assertEqualHTML(). There was a suggestion to split this into a dedicated ticket for clarity. Long-term plans include deprecating the function. Further discussion will continue in the ticket.
Fix for KSES inconsistencies
#63630: A pull request was introduced to correctly handle HTML entities for users without unfiltered_html. The 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. is under review, with attention on potential security and compatibility concerns.
Additional tickets
#22114 & #29798: Two open tickets were raised for feedback. For #29798, earlier comments advised against moving forward. The current PR only introduces user-facing messaging. If functional unification is planned, further adjustments will be needed.
Open Floor 🎙️
PHPMailer library proposal
#39714: A proposal to adopt the full PHPMailer library was reintroduced. The ticket has seen no recent activity. Feedback from previous maintainers was requested to move the discussion forward.
is_email() vs isEmail() behavior
#17491 and #24487: Differences between the Core is_email() function and @wordpress/url’s isEmail were brought up. Issues include support for IP address literals and IDNs. Existing related Trac tickets were referenced. The topic is broader and will be continued in the respective tickets.
