Gutenberg 23.7 Ships Its Last Fixes Before 7.1 RC1

🇹🇷 Türkçe: Bu yazının Türkçesini oku →

Every WordPress release cycle has a Gutenberg version that quietly does the last mile of cleanup before the RC branch closes. Nobody writes a launch video for it. It is the release that fixes the small things you would have spent a Saturday debugging.

Gutenberg 23.7 is that release for the 7.1 cycle. It shipped on August 5, the same day WordPress 7.1 RC1 went out and commits to trunk started requiring two committer sign-offs. That is not a coincidence. Everything that lands from here to the August 19 GA is either in this build or it is not going in.

I have been reading through the changelog with the same lens I read every pre-GA plugin update on a client estate: what breaks by default, what improves silently, and what I need to smoke-test before I let the auto-updater near production the week of the 19th. Here is the honest read.

What is actually new

The Gutenberg 23.7 release post by Jonathan Bossenger frames the version as “many improvements over features added with 23.6”, which is polite English for “we spent two weeks fixing the things reviewers found in the last plugin”. That is exactly what you want in the final pre-RC build.

Three changes deserve to be flagged by name. First, the Gallery block’s “Convert to images” action is gone, replaced by a button called “Detach” that opens a modal explaining what will happen (PR #80727). The old label had confused editors for years — you were not converting anything, you were breaking the gallery apart into free-standing image blocks with no undo grace. The new modal makes the decision explicit and the conversion collapses into a single undo level (PR #80665).

Second, the experimental “reflect inherited Global Styles values in block inspector controls” surface flipped from always-on to opt-in behind Gutenberg Experiments (PR #80815, tracking #77894). If you were relying on this to appear in every fresh install, it will not. If you were tripping over it in client demos where the inspector suddenly showed values the editor had not set, it will stop tripping.

Third, floated blocks no longer overlap sticky blocks in the editor canvas (PR #80749), and the Pullquote block finally honours its custom line height in the editor the same way it renders on the front end (PR #80586). Small on paper. Every agency that ships editorial layouts with pull quotes and floats knows how many “the editor looks different from the front end” tickets those two fixes retire.

Underneath the visible changes, the writing flow got quieter. Shift-arrow now extends block selections without dragging the native browser selection along (PR #80687). Page scroll no longer jumps during caret moves inside tall blocks (PR #80708). Forward-delete of empty blocks positions the cursor where a human would expect (PR #77525). The iOS jumping hack got removed and typewriter mode landed alongside (PR #74596). None of these will show up in a changelog headline. All of them matter more than the headline.

The Real-Time Collaboration surface, which was the marquee feature of Beta 1, got four production-grade fixes: collaborators’ unsaved edits are preserved when another user saves (PR #79936), Quick Edit is disabled while posts are actively being edited (PR #80016), controlled block synchronization no longer intercepts undo (PR #80503), and there is a serialization compaction pass (PR #80707). Notes-based async collaboration is what 7.1 is shipping to the wider public, but the RTC plumbing quietly hardened this cycle.

The context: WordPress 7.1 RC1 also shipped on August 5, with 145+ updates since Beta 4 per the release post. The RC phase note from Aaron Jorbin locked commit rules — every trunk commit now needs double sign-off from two core committers until the 7.1 branch is cut, with a hard string freeze already in effect. Milana Cap’s 7.1 Field Guide collates every dev note against 310+ Core Trac tickets. GA is August 19 at WordCamp US in Phoenix.

Why it matters for WordPress / WooCommerce people

Two things to internalise about this build.

One: this is the release surface that will land on production sites on August 19. Not the Beta 4 you tested three weeks ago, not the trunk you sync-pulled last night. Gutenberg 23.7 plus the RC-phase bug fixes over the next fourteen days is what your clients get. If you were counting on a fix that is not in this changelog, it is probably not shipping.

Two: the small stuff is the story. The Gallery “Detach” rename is one editor training session you no longer have to run. The pull-quote line-height fix is one class of client bug report you stop receiving. The typewriter mode on iOS is one reason mobile authors stop giving up halfway through a draft. Every one of these was on the “we’ll fix that eventually” list for years. This is the release where they came off.

For WooCommerce stores specifically, nothing in 23.7 touches Cart, Checkout, or the Store API. The Gallery Detach change is the one to flag with merchandisers who use gallery blocks for lookbooks or category headers — the label they knew is gone, the button in the same place does the same thing but now asks first.

What I would do (or not do) about it

Four moves this week, before the RC branch closes.

Install Gutenberg 23.7 on a staging clone of one representative editorial site and one representative WooCommerce site. Do the ten-minute smoke test: open a page with a Gallery block, click Detach, watch the modal, confirm the single-undo behaviour. Edit a post with a Pullquote using a custom line height, compare the editor to the front end. If both look the same, you know the two most visible visual regressions are gone.

If you were building against the experimental Global Styles inheritance UI, flip the Gutenberg Experiments toggle on your staging environment, confirm your dependency still resolves, and add a note to your build documentation that the flag is required. Silent opt-in flips are the kind of thing that eats a Tuesday morning in September when nobody remembers why the inspector looks different.

Do not run Gutenberg 23.7 in production on a WooCommerce store this week. WooCommerce 11.0 landed on August 4, WordPress 7.1 GA lands August 19, and the Gutenberg plugin on top of either is a third moving variable. Let 7.1 GA carry the backported subset. Uninstall the Gutenberg plugin from production sites before the 19th if you have not already — that has been the pattern for four releases now and nothing about this cycle changes it.

Do not install any plugin whose entire pitch is “adds a settings UI for Gutenberg experimental flags”. The flags are a checkbox screen inside Gutenberg itself, they are experimental on purpose, and wrapping them in a third-party layer that stores the state in a database option is the technical debt the experiments framework was designed to avoid.

The pipeline that produces one of these unglamorous cleanup releases every two weeks is the same pipeline that has kept WordPress upgradeable for two decades. Trust it, test it, and let the small fixes do their quiet work.