WordPress 7.1 Release Squad Sets August 19 Target

Every WordPress major has the same arc. There is a call for volunteers, then a quiet stretch where nothing seems to happen, then the squad is named and suddenly the whole project has a clock on it. We just hit that point for 7.1. From today, every plugin author, every theme team, every agency planning a Q3 launch has a fixed set of dates to plan against.

I have been through enough of these cycles to know the squad announcement is the moment to lock your own calendar, not to wait until beta 1 to start thinking about it. When the release lead is named, the cycle is real, and the eight weeks between now and the August target burn faster than any of us expect.

The good news this time is that the squad is small, the dates are already public, and the leadership leans on people who have done this before. Here is what was announced, what it means for the work we ship for clients, and what I would do this week if you maintain anything that touches WordPress core.

What is actually new

On June 17, 2026, Jeffrey Paul published the WordPress 7.1 release squad announcement on Make Core. Anne McCarthy is release lead. Benjamin Zekavica and Krupa Nanda handle release coordination. Aki Hamano and Joe Dolson are tech leads. Adrian Duffell, Sajjad Hossain Sagor, and Sergey Biryukov are triage leads. Huzaifa Al Mesbah and Nikunj Hatkar are test leads. The post notes that the number of volunteers far exceeded the available squad roles, which tells you something about contributor energy heading into this cycle.

The structure continues the streamlined approach used from 6.7 through 7.0 — fewer squad seats, more weight on collaboration with the Make Team Reps. That is a real change from the 5.x and early 6.x era, where the squad sometimes overlapped heavily with team rep responsibilities.

The dates were already set in the May 21 call for volunteers and reconfirmed on the WordPress 7.1 page on Make Core. The schedule is:

• Beta 1: July 15, 2026
• Beta 2: July 22, 2026
• Beta 3: July 29, 2026
• RC 1: August 5, 2026
• RC 2: August 12, 2026
• Dry run and code freeze: August 18, 2026
• Target final release: August 19, 2026

The squad inherits a Gutenberg pipeline that is moving fast. Gutenberg 23.4 shipped the same day as the squad announcement, with an experimental flag to test plugins, themes, and editor integrations against React 19, Site Editor color scheme respect, media editor improvements, Grid block transforms from Columns and Gallery, UltraHDR JPEG support, and reliability work on real time collaboration. React 19 itself was reverted in Gutenberg 23.3.2 after issues, with the commitment to land it cleanly inside the 7.1 window.

Real time collaboration is the other big thread. After being removed from 7.0, the collaborative editing outreach effort for 7.1 reopened public testing two weeks ago and the squad now owns the call on whether RTC ships in August or slips again.

Why it matters for WordPress and WooCommerce people

Three things change for working teams the moment a squad is named.

First, your plugin and theme support window has a hard edge now. Beta 1 is on July 15 — twenty-seven days from today. If you maintain anything non-trivial against WordPress, that is when you need to have a beta-tester environment running, automated tests pointed at the nightly, and the appetite to file Trac tickets the same day you find regressions. Waiting for RC means waiting four more weeks, and by then the bug you found is much harder to land a fix for.

Second, client launches in August become a real decision. We have one Istanbul client with a heavy WooCommerce migration scheduled for August 20. That is exactly one day after the target final ships. We are not going to be the team that goes live on a major WordPress release the day after it lands. The squad announcement is the cue to talk to that client today, not on August 5 when everyone is staring at RC 1.

Third, the React 19 and RTC stories tell you what the late-cycle drama is likely to be. Both have already slipped once. Both have committed contributor energy behind them. Both can produce last-minute revert decisions that change what 7.1 actually looks like on day one. If your stack depends on the block editor in ways that touch React internals — custom block UIs, complex InspectorControls, third-party React libraries — those are the bets you want hedged.

What I would do (or not do) about it

Three concrete moves this week.

Install the WordPress Beta Tester plugin on a staging copy of every project that matters. Set it to bleeding edge so it tracks nightlies between now and July 15, then to beta or RC after that. The whole point of the cycle’s test leads is to surface regressions early. The way you help them is by testing your own surface area on the nightly, not on the final.

Block the period from August 12 through August 26 in your launch calendar. Anything that absolutely must go live there should ship before August 12 or after August 26. Two weeks of buffer on either side of the final is the cheapest insurance in this business.

If you maintain a block plugin, turn on the Gutenberg 23.4 React 19 experiment on a dev site this week. The experiment is gated behind /wp-admin/admin.php?page=experiments-wp-admin and is the cleanest way to know whether your blocks survive the runtime swap before it becomes the default. Finding a React 19 incompatibility in July is fixable. Finding it on August 20 is a fire drill.

What I would not do is treat this squad announcement as marketing copy. The schedule is the actual product. Anne, Benjamin, Krupa, Aki, Joe, Adrian, Sajjad, Sergey, Huzaifa, and Nikunj now own the next eight weeks of the platform that runs roughly forty percent of the public web. The way agencies repay that is by showing up to the beta, not by waiting for the press release.

August 19 is sixty-two days away. The squad is set. The calendar is now yours to plan against, and the cheapest day to start is today.