The WordPress 7.0 release now has a final launch date: May 20, 2026. Anyone following the core Slack channel knows the mood there is cautious rather than celebratory. The latest Dev Chat agenda landed with a few technical pivots worth knowing about before trunk closes.
RC3 is the new Beta 1
The schedule for the WordPress 7.0 release has shifted. RC3, due May 8, is now being treated as the new Beta 1 for testing purposes, and the core team is specifically asking web hosts to test more. If you run high-traffic infrastructure, spin up a staging environment now and look for regressions in the block editor’s data-fetching logic.
The “temperature check” on the meeting agenda says something too. The project is on track, but the 7.0 milestones are complex enough to strain the CI/CD pipelines we have. I wrote about how these dates moved in my earlier breakdown of the WordPress 7.0 release date shift.
The Presence API feature plugin
The more interesting announcement is the Presence API Feature Plugin. It is a foundational layer for real-time awareness rather than another round of UI polish. Tracking who is editing what has meant leaning on transient hacks; the Presence API gives that data a dedicated wp_presence table instead.
Records carry a 60-second time-to-live (TTL). That is a pragmatist’s choice: it sidesteps the race conditions you get when several heartbeats fight over the same option row. A dedicated table also keeps awareness data out of wp_options, so it will not bloat that table or get wiped early when an object cache is flushed.
// 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?
The obvious question is why this does not use the Metadata API. The answer is performance. Writing heartbeat data to wp_usermeta every minute across a 100-user newsroom would fragment that table badly. A separate table with strict TTL logic lets the WordPress 7.0 release handle high-concurrency editing without wrecking database I/O.
If this WordPress 7.0 release work is eating your dev hours, I can take it on. I have been wrestling with WordPress since the 4.x days.
What to check before the May 20th launch
Spend the next two weeks on compatibility testing. The Presence API is experimental for now, but shipping it as a feature plugin points to where collaborative editing is headed. Watch the edit_posts capability gates, and make sure your custom admin screens are not firing awareness heartbeats where they should not.
