[desrosj]

What?

Migrates wp-env (packages/env) from Docker Compose v1 to v2, and fixes the database credentials mismatch the migration exposes.

Why?

Every wp-env job (PHP in unit-test.yml, Admin - 1 to Admin - 4 in end2end-test.yml) fails with spawn docker-compose ENOENT: packages/env runs the standalone Docker Compose v1 binary, which GitHub's runner images no longer ship. Trunk fixed the same problem in #51339 (WordPress@a0943f2, December 2023).

With that fixed, wp-env start reaches the database and fails at wp db check:

mariadb-check: Got error: 1045: Access denied for user 'example username'@'172.18.0.5' (using password: YES) when trying to connect

example username is the wordpress image's placeholder default, used when WORDPRESS_DB_USER/WORDPRESS_DB_PASSWORD are unset. No service on this branch sets them, while the mysql service (MYSQL_ALLOW_EMPTY_PASSWORD: 'yes') only has root with an empty password. This isn't a v2 regression; the v1 ENOENT failure hid it.

How?

• Migrate wp-env to Docker Compose V2.: adapts trunk's commit to this branch's files (lib/commands/{clean,destroy,logs,run,start,stop}.js, lib/wordpress.js, lib/cli.js). Each require( 'docker-compose' ) uses the v2 export; run.js spawns docker with compose prepended instead of docker-compose; cli.js's error message and its test/cli.js assertion say "docker compose". docker-compose (npm) is pinned to exactly 0.24.0, the newest release still on yaml@^1.10.2, the yaml line the rest of the lockfile uses; 0.24.1 and later move to yaml@^2.2.2, whose optional chaining Node 12 can't parse; the pin predates the Node 14 upgrade in Repair wp/5.6 branch Actions: Upgrade Node.js from 12 to 14 #334, and relaxing it is out of scope. package-lock.json gets a nested yaml@1.10.3 under docker-compose.
• Set explicit WORDPRESS_DB_USER/WORDPRESS_DB_PASSWORD on every service that talks to the database.: adds WORDPRESS_DB_USER: 'root' and WORDPRESS_DB_PASSWORD: '' to the wordpress, tests-wordpress, cli, tests-cli and phpunit services. Each container reads wp-config.php with its own environment, so all of them need it.

Verified on this fix's earlier unstacked PR (#284) with the react-native-screens fix (#294) applied: Install WordPress got past ENOENT and Access denied. At this point in the stack, CI jobs still stop at the npm ci failure fixed by #294, and then at the database setup that later PRs fix.

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.

[github-actions]

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 props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: desrosj <desrosj@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[desrosj]

Moved to WordPress#84961.