Repository navigation
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
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. |
5cea090 to
75bc860
Compare
|
Size Change: 0 B Total Size: 1.33 MB ℹ️ View Unchanged
|
75bc860 to
dc616f3
Compare
wp/6.2 branch Actions: Pin WordPress Core versionwp/6.2 branch Actions: Pin wp-env to the correct WordPress Core version
Part of #82931.
What?
Pins
wp-env's WordPress core checkout toWordPress/WordPress#6.2-branchvia.wp-env.json's"core"value, which was previously unpinned ("WordPress/WordPress"with no ref).Why?
Without a ref,
wp-envclonesWordPress/WordPress's default branch, so this frozen branch's PHPUnit tests ran against Core's trunk, which postdates, and can be incompatible with, the Gutenberg code being tested onwp/6.2. Pinning to the6.2-branchref keeps the core checkout aligned with the WordPress version this branch targets.wp/6.2'stest-phpjob has nowordpressmatrix dimension,WP_ENV_COREoverride orcompute-previous-wordpress-versionjob, so only.wp-env.jsonchanges.Use of AI Tools
This PR was created by Claude Code under my supervision. All code should be treated as AI-produced and not yet reviewed by a human until this PR is marked Ready for Review.