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.
This guide outlines major developer features and breaking changes in 6.8 and is published in the 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). phase to help inform WordPress extending developers, CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. developers, and others.
This release also includes 387 enhancements, 525 bug fixes, and 70 accessibility improvements for the 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 (a.k.a. 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/).
Below is a breakdown of the most important developer-related changes included in WordPress 6.8.
Table of contents
Block Editor
A wide array of improvements enhance performance, developer experience, and the overall editing interface. This release introduces new tools like the should_load_block_assets_on_demandfilterFilterFilters 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. for optimizing asset loading, a helpful warning system for developers using useSelect, and a more efficient block registration system. Additionally, it updates the design tool availability per block, polishes user interface components, and delivers a collection of miscellaneous refinements that improve consistency and extensibility.
Performance and Asset Loading
New tools support developers in building more performant block-based experiences. A warning in the useSelect hook alerts when selectors are defined inline—a common pattern that can lead to unnecessary re-renders. The should_load_block_assets_on_demand filter offers fine-grained control over whether block assets are enqueued globally or only when needed, helping reduce unused CSSCSSCascading Style Sheets. and 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/. on the front end. Together, these enhancements promote more efficient and optimized development workflows.
Improvements to block registration and design tool visibility streamline development and enhance clarity. A more efficient approach to block type registration reduces the overhead of loading block metadata, especially in environments with many custom blocks. Complementing this, the updated roster of design tools per block outlines which blocks support tools like padding, margin, and typography—giving developers a clearer picture of available customization options and improving consistency in the editor experience.
Refinements across the block editor interface improve consistency, usability, and developer ergonomics. Updates to core UI components—such as buttons, inputs, and layout primitives—align styling and behavior with the emerging 40px design system standard. Additional changes include improved markup consistency in the Navigation block, enhanced preview content for the Group block, and better 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) across interface elements. Together, these updates support a more polished and predictable editing experience.
A broad set of accessibility enhancements improves navigation, markup clarity, and screen reader support throughout the block editor. The .screen-reader-text class now offers more consistent focus behavior across components, while dozens of refinements address menu structures, block labels, tooltips, and interface semantics. These changes create a more inclusive editing experience and bring the block editor closer in line with accessibility best practices.
Several improvements to internationalization tooling and infrastructure enhance the translationtranslationThe process (or result) of changing text, words, and display formatting to support another language. Also see localization, internationalization. and localization experience for both developers and users. Updates include new and refined translation functions, consistency fixes, and improved support for plural forms—making it easier to build plugins, themes, and interfaces that are fully translatable and globally accessible.
New tools and guidance help developers build faster, more responsive experiences. The speculative loading feature leverages the Speculation Rules 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 prefetch or prerender likely navigation targets, improving perceived performance for end users. Additionally, updated best practices for the Interactivity API provide recommendations for writing efficient, scalable interactive front-end code—supporting modern, performance-focused development in WordPress.
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/.
Enhancements to the REST API expand its flexibility and usefulness for headless and decoupled WordPress applications. A new filter, rest_menu_read_access, allows developers to control public access to navigation menus, menu items, and menu locations via the REST API. This change enables more precise control over what menu data is exposed, supporting a wider range of front-end implementations and use cases.
Password security is strengthened with support for bcrypt as the new default hashing algorithm. This change modernizes WordPress’s password storage, offering improved resistance to brute-force attacks and aligning with current industry best practices. Existing passwords remain valid and will be rehashed with bcrypt upon the next successful login.
A range of smaller developer-focused updates improves consistency, extensibility, and the overall development experience. These changes span various areas of core, including media handling, shortcodeShortcodeA 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. output, post type registration, scheduling, and theme support. While individually minor, they collectively reflect ongoing efforts to modernize WordPress and provide a more predictable and flexible foundation for developers.
6.8 offers so much more! More than 170 bugs, 104 enhancements and feature requests, and 21 blessed tasks have been marked as fixed in WordPress 6.8. WordPress 6.8 will display Emoji 15.1’s new emojis for visitors not able to display them natively, such as the 🐦🔥.
Below are a few more to highlight:
Administration: Replace “Add New {Item}” wording with “Add {Item}” across the administration (#61219)
Bundled Theme: Improve text strings in Twenty Twenty-Five (#62482)
Bundled Theme: Accessibility additions to the site title link (#62895)
Date/Time: Date setting should have two more options: j.n.Y and d.m.Y (#55685)
Options, MetaMetaMeta 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. APIs: Rename the setted_transient action to set_transient (#62849)
REST API: Handle trailing slashes in rest_preload_api_request (#57048)
Security: Explicitly require the hashPHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher extension and add requirement checks during installation and upgrade (#56017)
Upgrade/Install: Prevent an unnecessary 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 update check when the plugin update data is up to date (#44118)
Widgets: Add post type support to get_calendar() function. This changeset also introduces a new get_calendar_args filter. (#34093)
Please, test your code. Fixing issues that your code has with WordPress core helps you and millions of WordPress sites. Please test your code.
