Weekly Summary
Article Inventory
- Bug Scrub Schedule for WordPress 7.1 (Make Core) — WordPress 7.1 bug scrubs transition from twice-weekly sessions to a daily schedule as the release date approaches, with a strict focus on fixing regressions rather than enhancements.
- WordPress 7.1 Release Party Schedule (Make Core) — WordPress 7.1 is scheduled for general release on August 19, 2026, following a release cycle that includes three beta phases, two release candidates, and a 24-hour code freeze starting August 15.
- X-post: Call for Testing: Responsive Styling (Make Core) — WordPress 7.1 introduces responsive styling, allowing users to apply specific styles to tablet and mobile breakpoints directly within the editor without writing custom CSS.
- Merge Proposal: Expanding WordPress Core Abilities (Make Core) — WordPress 7.1 will introduce three read-only abilities—
core/read-settings, core/read-content, and core/read-users—to provide a canonical baseline for agents and workflows to access site configuration, posts, and user data without re-implementing logic.
- Dev Chat summary: July 1, 2026 (Make Core) — The 7.1 release cycle includes a proposal to merge a new custom post type and hides the Classic block from the block inserter by default, with corresponding dev notes pending.
- What’s new in Gutenberg 23.5? (July 1, 2026) (Make Core) — Gutenberg 23.5 introduces experimental cropping controls to the Media editor and brings those capabilities to the Cover block, alongside new aspect-ratio and flex-alignment options for responsive styles.
- WordPress 7.0.1 RC1 is now available (Make Core) — WordPress 7.0.1 RC1 is a bug-fix-only maintenance release led by core contributors, intended to resolve issues introduced during the 7.0 cycle or intentionally deferred.
- Dev Chat Agenda – July 1, 2026 (Make Core) — The July 1, 2026, Dev Chat will address the 7.1 release roadmap, specifically reviewing a proposal to merge a new custom post type and confirming that the Classic block will be hidden from the inserter by default.
- Performance Chat Summary: 30 June 2026 (Make Core) — The June 30, 2026 Performance Chat confirms no tickets are available for the 7.0.1 release, so the "Awaiting Review" queue will be scrubbed and the meeting rescheduled for July 14, 2026.
- Guidelines for Syncing Code From Gutenberg Into WordPress Develop (Make Core) — During the 7.1 release cycle, code syncing from Gutenberg to WordPress trunk will occur one week after each Gutenberg general release to ensure trunk remains reasonably up to date.
- X-post: WordPress Credits Updates (Make Core) — The WP Credits program is shifting its 2026 focus from rapid growth to quality and retention, aiming to reach 35 school partnerships by year-end while establishing a public dashboard for impact tracking.
- The First AI Leaders Graduates (WordPress.org News) — On June 23, 40 students from UIC, Louisiana Tech, and UL Lafayette completed the AI Leaders Micro-Credential by building real projects with generative AI and contributing code to the WordPress open source ecosystem.
- ACF Chat Fridays: Introducing the ACF Data Store and Block Bindings UI (ACF Blog) — ACF 6.8.1 introduces a Data Store that enables real-time synchronization between ACF fields and the Gutenberg editor, resolving latency issues in block-based workflows.
- How WordPress Page Templates Actually Work (ACF Blog) — WordPress templates define the layout structure via a hierarchical fallback system, whereas individual pages store dynamic content, meaning template edits apply globally while page edits remain isolated.
- ACF 6.8.5 Security Release (ACF Blog) — ACF 6.8.5 addresses four critical security vulnerabilities: it restricts WooCommerce order field updates to authenticated users via HPOS, patches a stored XSS vector in the Flexible Content modal, enforces a 1000-choice limit for Checkbox/Radio/Select fields (customizable via
acf/fields/max_appended_choices), and ensures proper escaping of special characters in LIKE patterns.
- ACF Chat Fridays: Introducing the ACF Data Store and Block Bindings UI (ACF Chat Fridays) — ACF 6.8.1 introduces a Data Store that enables real-time synchronization between ACF fields and the Gutenberg editor.
Emerging Trends
- Shift to Daily Bug Scrubs for 7.1: The WordPress 7.1 release cycle is transitioning its bug scrub schedule from twice-weekly sessions to a daily cadence as the release date approaches, with strict focus on fixing regressions rather than adding features. Sessions are scheduled for July and August 2026 in the #core Slack channel, led by @sajjad67 and @adrianduffell.
- Release Timeline and Freeze: WordPress 7.1 is scheduled for general release on August 19, 2026. The cycle includes three beta phases, two release candidates, and a 24-hour code freeze starting August 15.
- Responsive Styling Integration: WordPress 7.1 introduces responsive styling, allowing users to apply specific styles to tablet and mobile breakpoints directly within the editor without writing custom CSS. PR #75121 unifies the resizable canvas with the device-preview switcher, meaning dragging resize handles now automatically updates the active viewport in the dropdown.
- Expansion of Read-Only Abilities: WordPress 7.1 will introduce three read-only abilities—
core/read-settings, core/read-content, and core/read-users—to provide a canonical baseline for agents and workflows to access site configuration, posts, and user data without re-implementing logic. This builds on the Abilities API from 6.9 by using a show_in_abilities flag to restrict exposure.
- Classic Block Deprecation: The 7.1 release cycle includes a proposal to hide the Classic block from the block inserter by default, with corresponding dev notes pending.
- Maintenance Release Schedule: WordPress 7.0.1 RC1 is available as a bug-fix-only maintenance release intended to resolve issues introduced during the 7.0 cycle or intentionally deferred.
- Gutenberg Sync Cadence: During the 7.1 release cycle, code syncing from Gutenberg to WordPress trunk will occur one week after each Gutenberg general release to ensure trunk remains reasonably up to date.
- ACF Performance Optimization: ACF 6.8.1 introduces a Data Store that enables real-time synchronization between ACF fields and the Gutenberg editor, resolving latency issues in block-based workflows.
- ACF Security Hardening: ACF 6.8.5 addresses four critical security vulnerabilities, including restricting WooCommerce order field updates to authenticated users via HPOS, patching a stored XSS vector in the Flexible Content modal, and enforcing a 1000-choice limit for Checkbox/Radio/Select fields.
Developer Implications
- Monitor Daily Scrubs for 7.1: Freelance and agency developers should monitor the #core Slack channel for updates on the daily bug scrub schedule for WordPress 7.1 (July and August 2026) and join the appropriate component channels (accessibility, performance, testing) to triage reported issues.
- Prepare for August 19 Release: Teams should prepare for the WordPress 7.1 general release on August 19, 2026, noting the 24-hour code freeze starting August 15. The release squad will coordinate milestones via the #core Slack channel and a live WordCamp US 2026 event.
- Test Responsive Styling in Playground: Developers should test the new responsive styling feature in the WordPress Playground. Specifically, verify that per-breakpoint edits are preserved correctly and that the "Responsive editing" toggle properly isolates styles for specific devices, as the canvas resizing logic has changed.
- Audit Read-Only Abilities: Developers building AI clients or external workflows should audit their code against the new read-only abilities (
core/read-settings, core/read-content, core/read-users) introduced in 7.1. Ensure they are using the show_in_abilities flag to restrict exposure and prevent data leakage, as this replaces the need to re-implement logic for accessing site configuration and content.
- Plan for Classic Block Removal: If your agency or client sites still rely on the Classic block, you must plan for its removal from the block inserter by default in the 7.1 release. You should migrate content to the block editor before the release to avoid functionality loss.
- Update to 7.0.1 RC1: If you are running WordPress 7.0, you should test and apply the 7.0.1 RC1 release immediately to resolve known issues with Twemoji replacement logic, PHP 8.5 array access errors in
wp_get_attachment_image_src, and accessibility regressions in the Visual History block.
- Sync Gutenberg Code: If you are maintaining a custom Gutenberg block plugin, ensure your code is synced to WordPress trunk one week after each Gutenberg general release to maintain compatibility with the upcoming 7.1 cycle.
- Upgrade ACF to 6.8.5: Agencies using Advanced Custom Fields should upgrade to version 6.8.5 immediately to patch critical security vulnerabilities, including the stored XSS vector in the Flexible Content modal and the restriction of WooCommerce order field updates.
- Leverage ACF Data Store: When building block-based workflows with ACF, utilize the new Data Store introduced in ACF 6.8.1 to ensure real-time synchronization between ACF fields and the Gutenberg editor, eliminating latency issues.
Since Last Report
- New topic: Bug Scrub Schedule for WordPress 7.1 (Make Core) — WordPress 7.1 bug scrubs transition from twice-weekly sessions to a daily schedule as the release date approaches, with a strict focus on fixing regressions rather than enhancements.
- New topic: WordPress 7.1 Release Party Schedule (Make Core) — WordPress 7.1 is scheduled for general release on August 19, 2026, following a release cycle that includes three beta phases, two release candidates, and a 24-hour code freeze starting August 15.
- New topic: X-post: Call for Testing: Responsive Styling (Make Core) — WordPress 7.1 introduces responsive styling, allowing users to apply specific styles to tablet and mobile breakpoints directly within the editor without writing custom CSS.
What I'm Watching
The new ACF DataStore (in ACF PRO preview) is a handy tool for managing global or reusable field data in WordPress, separate from individual posts. It enables cleaner organization and more flexible storage of configuration-like custom field values.
Responsive Styling needs your testing! 🥳 The long awaited enhancements for responsive styling are ready for testing and feedback. Please test and provide feedback.
Source Articles
Make Core
WordPress.org News
ACF Blog
ACF Chat Fridays
Build Notes
- Articles analyzed: 16
- Sources: Make Core, WordPress.org News, ACF Blog, ACF Chat Fridays
- Model: openai-compatible/qwen/qwen3.5-9b
- Tokens: 15864 prompt + 2697 completion
- Estimated cost: $0.00 (local model)
- Review time: (add after human review)