While WordPress 7.1.1 is shaping up as a small bug-fix release due September 17, the Gutenberg team hasn’t slowed down on new editor features. Version 23.8 shipped an improvement editors have wanted for a while: visual revisions of content now get their own shareable URL. And WordPress 7.2 is already on the horizon, with a beta scheduled for October 20–22.
Revisions with their own link and a diff view
Visual revisions let you browse a post’s edit history inside the editor in the same visual layout readers will actually see — not just a dry text diff. Gutenberg 23.8 takes this further: every individual revision now has its own URL that you can send to a colleague or client for feedback, without them having to dig through the whole history manually. The release also adds an in-editor code diff view, especially handy for developers working with custom blocks or raw HTML inside posts.
For editorial teams and agencies publishing content for clients, this means a faster approval process. Instead of screenshots or “please go back to version three,” you can simply share a link straight to the exact revision.
More from Gutenberg 23.8 and 23.9
Alongside revisions, this release added email notifications for @mentions in comments, and dramatically improved List View performance on large posts — long articles used to visibly lag when browsing blocks, and navigation is now much smoother even on pages with dozens of sections. The following 23.9 release builds further on these performance improvements.
WordPress 7.2 is taking shape for October
After WordPress 7.1 “Mary Lou” introduced responsive style states and icon registration, a minor bug-fix release, 7.1.1, is due September 17. The real next step comes a month later: WordPress 7.2 beta is scheduled for October 20–22, with the stable release planned between December 8 and 10. Many of the features currently being tested in Gutenberg 23.8 and 23.9 are expected to land in WordPress core with 7.2.
For site owners, this means one thing: if you’re planning bigger site changes around year-end, expect a new WordPress major release in December. Before deploying it to a production site, it’s always wiser to wait for the first patch release (e.g. 7.2.1) and test plugin compatibility on a staging environment first.
Conclusion
WordPress development doesn’t pause between major releases — small improvements like shareable revision links can save real time in everyday content work. Want to make sure your site handles the move to WordPress 7.2 without a hitch? Get in touch — we’re happy to help with the update and testing.
