Here is the WordPress 6.9 field guide – round-up of developer features.

Round-up of WordPress 6.9 Developer Features
Amy Kamala @ make.wordpress.org • 3 hours ago

Amy Kamala @ make.wordpress.org • 3 hours ago
Here is the WordPress 6.9 field guide – round-up of developer features.

David Levine @ rtcamp.com • 3 days ago
Wondering what the Abilities API is that is coming in WordPress 6.9? This article does a nice job of explaining it.

John Blackbourn @ make.wordpress.org • 4 days ago
Nice, PHP 8.5 was released on November 20th and WordPress 6.9 RC2 already has support for it.

Dennis Snell @ make.wordpress.org • 1 week ago
The changes described in this dev note sound like good ideas, but people should be sure to test mail sending and not assume it is going to work.

Roger Montti @ searchenginejournal.com • 2 weeks ago
WordPress 6.9 will include the Abilities API that looks to be a big feature for developers. This article by Roger Montti does a good job of explaining what it is and its advantages. It is worth a read even if you aren’t a developer as I imagine it will be widely implemented.

André Maneiro @ make.wordpress.org • 2 weeks ago
This is a round-up post of the changes related to the Fields API and DataViews that are coming in WordPress 6.9. It looks like the Fields API is maturing. The Fields API may become significant in the future for those interested in dynamic data.

Akshaya Rane @ make.wordpress.org • 1 month ago
The first beta of WordPress 6.9 is available. This release is not earth shattering, but it has a lot of nice enhancements. Some of the highlights are: notes can be attached to individual blocks for collaboration, there are several new blocks, and the Command Palette has been expanded.

John Blackbourn @ wordpress.org • 2 months ago
WordPress 6.8.3 is rolling out now. It is a security release and the core team is recommending that people update their sites now.

Patchstack Researchers @ patchstack.com • 2 months ago
Patchstack is now reporting 2 low severity vulnerabilities for WordPress 6.8.2. The first is a Cross-Site Scripting issue that requires the attacker to have an Author or higher privilege level to exploit. The second is a Sensitive Data Exposure issue that requires Contributor level access to exploit.