Fix WordPress 7.0 preview and test configs#626
Conversation
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
6031c83 to
8d898c3
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #626 +/- ##
=============================================
+ Coverage 74.00% 74.45% +0.45%
- Complexity 1738 1740 +2
=============================================
Files 85 85
Lines 7490 7521 +31
=============================================
+ Hits 5543 5600 +57
+ Misses 1947 1921 -26
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
| const blueprint = { | ||
| preferredVersions: { | ||
| wp: 'beta', | ||
| wp: '7.0', |
There was a problem hiding this comment.
We shouldn't specify a version here as this will get out of date whenever a new version is released. I think we'd want latest
| "preferredVersions": { | ||
| "php": "7.4", | ||
| "wp": "beta" | ||
| "wp": "7.0" |
There was a problem hiding this comment.
Similar to above, this should be latest I think

What?
Closes #623
Updates the Playground, Plugin Check, PHPUnit, and wp-env configs now that WordPress 7.0 is available as the latest stable release.
Why?
The AI plugin requires WP 7.0, but some configs still contained temporary pre-release or trunk settings that were added before WP 7.0 was released.
This could cause the AI plugin Playground preview to load WP 7.0 RC5 instead of the final WP 7.0 release. Now that 7.0 is released, these configs can use stable release defaults again while keeping explicit trunk coverage where it is still useful.
How?
7.0.7.0.latest.latestandtrunk..wp-envconfigs tocore: null, which uses the latest production WordPress release.Use of AI Tools
AI assistance: Yes
Tool(s): Codex
Model(s): GPT-5
Used for: Identifying the affected config files, preparing the local patch, and drafting validation steps. The changes were reviewed and confirmed by me.
Testing Instructions
Screenshots or screencast
Not applicable. This is a configuration-only change.
Changelog Entry