Repair wp/6.1 branch Actions: Replace wp-env's database check with a MariaDB health check - #592

What?

Ports WordPress#75046 ("wp-env: Fix MySQL startup race condition causing database connection errors") to this branch's wp-env:

• The database services (mysql and tests-mysql) get a health check. It is Env: Add an option to choose the MariaDB version WordPress/gutenberg#83751's runtime check, kept in one MARIADB_HEALTHCHECK constant: it runs MariaDB's healthcheck.sh --connect --innodb_initialized only when the data directory has .my-healthcheck.cnf and the image has healthcheck.sh, and otherwise pings the server over TCP on 127.0.0.1 with mariadb-admin or mysqladmin. MARIADB_AUTO_UPGRADE is set so existing databases get the user healthcheck.sh needs.
• wordpress and tests-wordpress depend on their database with condition: service_healthy, so Docker Compose only starts WordPress once MariaDB is ready.
• The wp db check connection check, its 30-second retry loop and the extra 4-second sleep are removed from wp-env start.
• wp-env start starts mysql and tests-mysql together, and wp-env clean starts only the database(s) it resets.
• packages/env/CHANGELOG.md gets trunk's entry, extended to describe the ping fallback, with links to wp-env: Fix MySQL startup race condition causing database connection errors WordPress/gutenberg#75046 and Env: Add an option to choose the MariaDB version WordPress/gutenberg#83751.
• The README note about wp db commands with MariaDB servers before 11.4 now says that wp-env start is not affected either, since it no longer runs wp db check.

Why?

wp db check runs mariadb-check in the cli container. The client in the current wordpress:cli image (MariaDB 11.8) requires TLS by default, and WP-CLI runs it with --no-defaults, so nothing can turn that off. MariaDB releases before 11.4 have no TLS unless it's configured, so the check fails with TLS/SSL error: SSL is required, but the server does not support it and wp-env start stops. #585 pins MariaDB 10.6, which is one of those releases, so every job that starts wp-env fails.

trunk removed wp db check in WordPress#75046 and waits for MariaDB with a health check instead, which doesn't use the MySQL client at all.

How?

The depends_on, start and clean changes follow WordPress#75046 hunk for hunk, adapted to this branch's file layout (commands/start.js, commands/clean.js and wordpress.js).

The health check command is WordPress#83751's rather than WordPress#75046's, because running healthcheck.sh unconditionally doesn't work with every version the MariaDB version setting can select:

• The MariaDB 10.2 and 10.3 images ship healthcheck.sh without the healthcheck user, so the script fails.
• Images built before 2022, and old patch tags such as 10.5.8 and 10.6.4, have no healthcheck.sh.
• .my-healthcheck.cnf lives in the data volume, so it is still there when an older image without the script runs on a volume a newer image wrote. Checking only for the file would then run a missing command (exit code 127).

The fallback uses mariadb-admin when the image has it (11.0 and newer only ship that name) and mysqladmin otherwise (versions before 10.4 only ship that name). It connects to 127.0.0.1 over TCP rather than the Unix socket, which the temporary server that initializes a new volume answers before the real server is listening.

Testing:

• wp-env: Fix MySQL startup race condition causing database connection errors WordPress/gutenberg#75046's two compose-builder tests are ported, along with Env: Add an option to choose the MariaDB version WordPress/gutenberg#83751's health check tests, which run the command through /bin/sh with stub healthcheck.sh, mariadb-admin and mysqladmin scripts (skipped on Windows). They replace $$ with .split().join() instead of replaceAll, which Node 14 doesn't have. npm run test-unit -- packages/env passes all 107 tests locally.
• A local wp-env start with "mariadbVersion": "10.6" succeeds: both database containers report healthy and WordPress installs in both environments. With mariadb:10.3, which has no healthcheck user, both databases become healthy through the ping fallback.

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.