WordPress 7.1 hit Beta 1 this week, locking in a release date along with a first look at responsive styling and a cleaner toolbar. Not everything survived the cut: co-founder Matt Mullenweg vetoed a bigger AI storage feature planned for core, and the security team detailed 18 months of work hardening WordPress’s build pipeline. WooCommerce also shipped two updates worth a look if you run a store.
Block Editor: Beta 1 locks in the feature list
WordPress 7.1 hit its first beta this week, locking in the feature list for a final release on August 19. Beta 1 is for testers only. Do not install it on a live site; use a local install, a staging site, or WordPress Playground instead.
Beta 1 also cleans up navigation in the Post and Site Editors. The confusing “W” logo back button is gone, replaced with a chevron, and the toolbar now shows by default the way it does everywhere else in wp-admin.
The headline addition is responsive styling, a long-requested feature that lets you set how a block looks on different screen sizes directly in the editor, with no custom CSS required. It ships alongside client-side media processing, which moves image handling into the browser with broader format support including HEIC and AVIF, plus two new blocks, Playlist and Tabs. Full details are in WordPress’s Beta 1 announcement.
AI: Mullenweg vetoes a core knowledge feature
Not every proposed 7.1 feature made it through. Mullenweg vetoed a plan to merge a new wp_knowledge post type and a Guidelines feature into core, five days before Beta 1 shipped.
Guidelines would give site owners a settings page to store content standards, such as preferred tone of voice or terminology, that writers, editors, and AI tools could all reference. The proposal went further and tried to bundle that into a broader storage primitive meant to also hold AI agent notes and memory. Mullenweg’s team said he wants AI features in core to show real-world adoption with double-digit weekly growth before they land, and this proposal wasn’t there yet. If you’re experimenting with AI workflows on WordPress, expect Guidelines to keep developing as a plugin rather than arrive in core anytime soon.
Security: 18 months of hardening WordPress’s build pipeline
The WordPress Security Team detailed 18 months of work hardening the GitHub Actions workflows that build, test, and release WordPress code, the same kind of automation that attackers have exploited in recent supply-chain attacks against other open source projects.
The work added two automated scanners that check workflow files for weaknesses, and the team now wants that scanning enforced across every repository in the WordPress GitHub organization rather than repo by repo. WordPress’s bug bounty program was also updated in May to cover build automation, not just the software itself. None of this requires action from you, since it’s WordPress hardening its own infrastructure rather than something on your site, but it’s a reassuring sign given how many plugin backdoor incidents have surfaced across the ecosystem this year.
Business: WooCommerce ships two store-owner updates
WooCommerce shipped two updates aimed squarely at store owners this week. A free Reddit Ads extension folds account setup, pixel tracking, and catalog sync into your store dashboard, useful if your products are the kind people research on Reddit before buying.
WooCommerce also explained how it’s fixing a problem with its AI support assistant, which was giving confident but outdated answers because product changes weren’t reaching the documentation fast enough. The fix is a review pipeline that drafts documentation updates automatically but still requires human approval before anything publishes. It’s worth remembering the next time any AI tool gives you store instructions: check that what it describes actually matches what’s on your screen.
End of article