Repair wp/5.5 branch Actions: Add a WP_ENV_MARIADB_VERSION environment variable - #576

What?

Adds a WP_ENV_MARIADB_VERSION environment variable that picks the MariaDB image wp-env uses: packages/env/lib/build-docker-compose-config.js changes 'mariadb' to 'mariadb:${WP_ENV_MARIADB_VERSION:-latest}', so the default image doesn't change.

• README: documents the variable next to the port variables. Downgrading needs wp-env destroy, since MariaDB can't start on a database written by a newer version. With a version older than 11.4, wp db commands in the cli and tests-cli containers fail and wp-env clean leaves the database alone, because the wordpress:cli image's MariaDB client requires TLS; WordPress itself isn't affected.
• CHANGELOG: a New Features entry.
• Test: a new case in packages/env/test/build-docker-compose-config.js checks the image string.

Why?

This branch's wp-env (1.6.0) always runs the floating mariadb image, many years newer than anything this branch was tested against, with no way to pin an older one.

How?

Follows WordPress#83751, which adds a mariadbVersion option and this environment variable to trunk. wp-env 1.6.0 has no version settings to extend, so only the variable is ported. Docker Compose substitutes it when it reads the generated file, as it already does for WP_ENV_PORT and LOCAL_PHP.

npm run test-unit -- packages/env passes all 31 tests locally (packages/env/test/cli.js can't load without a built nodegit, which is unrelated).

The mariadb-check TLS error wp-env start hits with older MariaDB versions is fixed by #598, two PRs above.

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.

🤖 Generated with Claude Code