The WordPress 7.0 release is officially barreling toward us, with the final launch date set for May 20, 2026. However, if you’ve been following the core Slack channel, you know that the “vibe” in the room is one of cautious urgency. We just saw the latest Dev Chat agenda drop, and there are a few technical pivots that every senior developer needs to have on their radar before the trunk closes.
The Timeline Pivot: RC3 is the New Beta 1
In a move that feels very much like a “refactor on the fly,” the schedule for the WordPress 7.0 release has been adjusted. RC3 is now being treated as the “new Beta 1” for testing purposes, scheduled for May 8. Specifically, the core team is calling for web hosts to step up their testing. If you are managing high-traffic infrastructure, you should be spinning up staging environments now to check for regressions in the block editor’s data-fetching logic.
Furthermore, the “temperature check” mentioned in the meeting agenda is telling. It’s an admission that while we are on track, the complexity of the 7.0 milestones is testing the limits of our current CI/CD pipelines. For a deeper look at how these dates have shifted recently, check out my previous breakdown on the WordPress 7.0 release date shift.
Deep Dive: The Presence API Feature Plugin
The most intriguing technical announcement is the introduction of the Presence API Feature Plugin. This isn’t just another UI polish; it’s a foundational layer for real-time awareness. Instead of relying on messy transient hacks to track who is editing what, the Presence API introduces a dedicated wp_presence table.
Technically, the API uses a 60-second Time-to-Live (TTL) for records. This is a pragmatist’s choice—it avoids the race conditions often found when multiple heartbeats try to update the same option row. From an architectural standpoint, having a dedicated table ensures that awareness data doesn’t bloat your wp_options or get wiped prematurely during an object cache flush.
// Example of how the Presence API might be queried via WP-CLI
// to check active sessions on the 7.0 branch.
wp presence list --fields=user_id,screen,last_active --format=tableWhy a Dedicated Table?
Many devs might ask why we aren’t using the Metadata API here. The answer is performance. Writing heartbeat data to wp_usermeta every minute across a 100-user newsroom would create massive table fragmentation. By using a separate table with a strict TTL logic, the WordPress 7.0 release aims to support high-concurrency editing without killing the database’s I/O.
Look, if this WordPress 7.0 release stuff is eating up your dev hours, let me handle it. I’ve been wrestling with WordPress since the 4.x days.
Takeaway for the May 20th Launch
Consequently, your focus for the next two weeks should be on compatibility testing. The Presence API is experimental for now, but its inclusion as a feature plugin suggests it’s the future of how we handle collaborative editing. Therefore, keep an eye on the edit_posts capability gates and ensure your custom admin screens aren’t accidentally triggering awareness heartbeats where they shouldn’t.
