WordPress 7.1 RC1: What to Test Before the Final Release

WordPress 7.1 Release Candidate 1 (RC1) includes more than 145 changes made after Beta 4: 57 in the Editor and 88 in WordPress core. It is the first release candidate ahead of the planned WordPress 7.1 final release on August 19, 2026.

RC builds are still development software. Keep RC1 off production and mission-critical sites, and use an isolated test server or test site instead.

Install WordPress 7.1 RC1 for testing

You can run RC1 through a beta-testing plugin, a ZIP install, WP-CLI, or a browser-based WordPress Playground instance. Pick the route that best matches the environment you need to validate.

1. Install and activate the WordPress Beta Tester plugin on a WordPress install. Set its channel to Bleeding edge and its stream to Beta/RC Only.
2. Download the RC1 ZIP and install it on a WordPress website.
3. Update from the command line with WP-CLI.
4. Open the provided WordPress Playground instance to test in a browser without local setup.

wp core update --version=7.1-RC1

wp core update --version=7.1-RC1

The WordPress 7.1 release schedule has the complete milestone timeline. For broader release context, use the Beta 1 announcement, the WordPress 7.1 Dev Notes, and the WordPress 7.1 Field Guide.

Features added after Beta 1

RC1 brings APIs and configuration surfaces that plugin, theme, and hosting developers should review alongside the Editor changes. These additions arrived during the 7.1 cycle after Beta 1.

• Icons API: WordPress core now has APIs to register icons and icon collections, with an extension point for plugins. See changeset 62748.
• Speculative loading configuration: Environment variables and constants can configure the defaults for speculative loading. See ticket 65624.
• Email notifications for @mentions: A user mentioned in a Note can receive an email notification. See pull request 79606.
• Shareable Revisions: Specific revisions can be shared through links to make collaboration quicker. See pull request 79934.

Editor, REST API, and core changes to validate

Several late-cycle changes affect block editing, content selection, REST API loading, sanitization, multisite media handling, and bundled JavaScript libraries. Include the areas that match your code paths in your compatibility checks.

• GB-79839: The global application flow lets users choose which changed block styles to apply.
• GB-80814: The responsiveEditingEnabled editor setting can hide responsive styles.
• GB-80107: Tabs get toolbar controls for changing tab order.
• GB-80046: DataViews supports range selection with Shift-click.
• 65636: REST API requests fetched when the editor loads are preloaded.
• 65613: Notes no longer appear in comment feed queries.
• 65491: KSES permits the autofocus attribute on dialog elements.
• 65517: A multisite installation enforces upload limits when media is sideloaded from a URL.
• 62757: The bundled jQuery UI library is updated to version 1.14.2.

For the full set of issues resolved after Beta 4, inspect the 7.1 GitHub commits since July 29, 2026 and the closed WordPress 7.1 Trac tickets from July 29 through August 5, 2026.

Finish plugin and theme compatibility checks

RC1 is the point to complete 7.1 compatibility testing for your plugin or theme. Test both the upgrade path and the features your product uses, including the Editor behavior and WordPress core changes relevant to it.

After validation, set the Tested up to value to 7.1 in your plugin’s readme file. If you identify a compatibility problem, file detailed information in the Alpha/Beta support forum.

Prepare your test environment now

Start with a disposable copy of a representative site, test the upgrade, and exercise the plugin, theme, multisite, media, and editor workflows that matter to your deployment. If your environment matches the expected behavior, update the plugin readme’s Tested up to field before the August 19, 2026 release target.