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 |
|
Size Change: 0 B Total Size: 1.23 MB ℹ️ View Unchanged
|
|
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. |
7211376 to
4b2d02a
Compare
|
Size Change: 0 B Total Size: 1.23 MB ℹ️ View Unchanged
|
4b2d02a to
3b5f211
Compare
|
Size Change: 0 B Total Size: 1.23 MB ℹ️ View Unchanged
|
3b5f211 to
cb88be8
Compare
Part of #82933.
What?
Migrates
wp-env(packages/env) from Docker Compose v1 to v2.Why?
Every
wp-env-dependent job in this branch's CI (end2end-test.yml'sAdmin - NPuppeteer jobs,end2end-test-playwright.yml'sE2E TestsPlaywright job, andunit-test.yml'sPHPjob) fails withspawn docker-compose ENOENT. The root cause:packages/envshells out to a literaldocker-composebinary — the standalone Docker Compose v1 CLI — which GitHub's current runner images no longer ship. Runners only provide Compose v2 today, invoked either as thedocker composesubcommand directly, or via the npmdocker-composelibrary'sv2export.This is a straightforward, previously-solved problem: trunk hit and fixed the identical issue in commit a0943f2 ("wp-env: Migrate to Compose V2 (#51339)", #51339), merged December 2023.
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.