WORDPRESS
May 12/2026

Exploring the innovative features of WordPress 6.5.

8 min read
Author
ABHILASH
Devops Engineer
Share this article
Featured
CloudStick
WordPress migrations

Introduction

WordPress 6.5, codenamed Regina after the jazz violinist Regina Carter, landed on April 2, 2024 — and quietly turned out to be one of the most developer-focused releases in years. Where 6.4 was about polish, 6.5 is about capability: a real font system, a first-class interactivity primitive, formal plugin dependencies, and tooling that finally makes block themes feel like a coherent platform rather than a Gutenberg side-project. If you run any meaningful amount of WordPress on CloudStick, the upgrade is worth doing today rather than waiting for 6.5.x. Here's what's actually different — and where to be careful.

PREREQUISITE

WordPress 6.5 requires PHP 7.2+ and MySQL 5.7+ (or MariaDB 10.3+). CloudStick's EasyPHP gives you PHP 8.4 by default on new servers — you don't have to touch a thing.

Font Library

Finally, a way to manage fonts that doesn't involve manually editing theme.json or writing custom functions. The Font Library is a first-class UI inside the Site Editor that lets you upload, activate, and deactivate fonts across your entire site. Google Fonts are available directly from the panel. Custom fonts are stored in the uploads directory and referenced in theme.json automatically.

The whole thing is opt-in: you mark a block with thecore/interactivitynamespace

declare a tiny state object, and bind directives in the markup:

1. Interactivity API

Probably the most consequential change for developers. The Interactivity API is a small reactive runtime — think Alpine.js but built-in — that ships with every WordPress install. It lets you wire up live blocks (carousels, filters, inline cart updates, live search) without dragging in React or hydration toolchains.

The whole thing is opt-in: you mark a block with thecore/interactivitynamespace

declare a tiny state object, and bind directives in the markup:

// view.js
import { store, getContext } from '@wordpress/interactivity';
store('cloudstick/counter', {
actions: {
increment() {
const ctx = getContext();
ctx.count += 1;
},
},
}),

The Interactivity API isn't trying to replace React. It's trying to make 80% of “add a tiny bit of behaviour to this block” cases possible without picking a framework. That's the right scope.

2. Plugin Dependencies

Probably the most consequential change for developers. The Interactivity API is a small reactive runtime — think Alpine.js but built-in — that ships with every WordPress install. It lets you wire up live blocks (carousels, filters, inline cart updates, live search) without dragging in React or hydration toolchains.

The whole thing is opt-in: you mark a block with thecore/interactivitynamespace

declare a tiny state object, and bind directives in the markup:

TIP

If your site relies on a font-loading plugin like OMGF or Local Google Fonts, deactivate it before upgrading.

3. Block bindings API

Probably the most consequential change for developers. The Interactivity API is a small reactive runtime — think Alpine.js but built-in — that ships with every WordPress install. It lets you wire up live blocks (carousels, filters, inline cart updates, live search) without dragging in React or hydration toolchains.

The whole thing is opt-in: you mark a block with thecore/interactivitynamespace

declare a tiny state object, and bind directives in the markup:

// view.js
import { store, getContext } from '@wordpress/interactivity';
store('cloudstick/counter', {
actions: {
increment() {
const ctx = getContext();
ctx.count += 1;
},
},
}),

Synced Patterns & Rest

Synced patterns (formerly Reusable Blocks) get a proper management UI. Unsynced copies are now first-class, so you can detach a pattern and edit it independently without wrestling with the block editor. The REST API also gains batch endpoint support, shaving round-trips for headless builds that need multiple resources simultaneously.

Final thoughts

6.5 is the most quietly important WordPress release since the introduction of Gutenberg. The Font Library and Block Bindings together remove two of the three reasons we used to reach for ACF on every new site. The Interactivity API is the first time WordPress has shipped a coherent answer to the “how do I add dynamism without a SPA” question. Plugin Dependencies will silently prevent the next 100,000 white-screens. Upgrade your staging this week. Promote next week. Don't wait for 6.5.4.

Leave a comment
Full Name
Email Address
Message
Contents

We use cookies to improve your experience

CloudStick uses cookies to personalise content, analyse traffic and keep you signed in. Cookie Policy · Terms of Service

Manage cookies