WordPress 6.5

WordPress 6.5 expanded the block editor and site-building APIs rather than changing the basic WordPress operating model. It introduced the Font Library for managing fonts in supported themes, added the Block Bindings API for connecting block attributes to data from custom sources, and added the Interactivity API for building interactive block experiences with a standard client-side approach. It also added a plugin dependencies mechanism, AVIF image support where the server supports it, and editor, performance, accessibility, and developer-tooling improvements. WooCommerce is a plugin that runs on WordPress, so a WooCommerce store is a WordPress site and its WordPress version matters as much as its WooCommerce version.

WordPress 6.5 has reached end of life. Remaining on it means the site does not receive fixes delivered in later WordPress maintenance and security releases, including fixes for core defects that can affect administration, content editing, REST API use, media handling, and authentication-related behavior. The practical risk increases as plugins, themes, hosting stacks, PHP versions, and WooCommerce extensions move their tested and supported baselines forward. A site may continue to operate, but a future plugin, theme, or server change can expose compatibility problems that are harder to diagnose because the core version is no longer maintained. For WooCommerce sites, outdated WordPress core can also constrain upgrades to the store plugin and its extensions, leaving payment, checkout, fulfillment, and administrative workflows on older dependency combinations.

Plan an upgrade from 6.5 to the current supported WordPress release, using a staging copy that includes the production database, uploads, active theme, custom code, plugins, and WooCommerce extensions where applicable. Before upgrading, take verified database and file backups and document a rollback procedure. Review PHP, database, web-server, and caching compatibility for the target WordPress version; update unsupported plugins and themes first or replace abandoned ones. Test critical workflows after the core upgrade, including login and user roles, publishing, forms, search, media uploads, scheduled tasks, integrations, backups, caches, and any custom REST or block-editor features. For WooCommerce, additionally test product management, tax and shipping calculations, payment authorization and refunds, cart and checkout behavior, customer emails, order administration, subscriptions or bookings, and external fulfillment or accounting connections. Apply the upgrade to production in a controlled maintenance window, then review logs, error reporting, and key transactions after deployment.