[desrosj]

What?

Adds a mariadbVersion option to .wp-env.json and a WP_ENV_MARIADB_VERSION environment variable, so the MariaDB version wp-env uses can be chosen.

• The option can be set at the top level or per environment (env.development, env.tests), like phpVersion.
• WP_ENV_MARIADB_VERSION overrides both environments.
• Accepted values are "lts", "latest", or a numeric version such as "10.11" or "11.4.2". Anything else fails with a validation error, including an invalid WP_ENV_MARIADB_VERSION value.
• When no version is set, the database image stays mariadb, exactly as before. A set version becomes mariadb:<version> on the mysql and tests-mysql services.

The README gets a table row and a "Specific MariaDB Version" section, and packages/env/CHANGELOG.md gets an entry under Unreleased.

The README section also says:

• MariaDB cannot start on a database written by a newer version, so before switching to a lower version, run wp-env destroy. It removes the environment's Docker containers, volumes, networks, and local files, not only the databases.
• With a mariadbVersion older than 11.4, wp db commands in the cli containers fail and wp-env clean leaves the database as it is. The MariaDB client in the CLI image requires TLS when phpVersion is unset or 8.1 or newer, and MariaDB servers before 11.4 do not offer it. WordPress itself is not affected.
• MariaDB 5.5 images are not published for ARM processors. Apple silicon devices can run 5.5 under emulation with DOCKER_DEFAULT_PLATFORM=linux/amd64, which emulates every container in the environment, not only the database.

Why?

This branch's wp-env (4.1.3) always runs the floating mariadb image, which today is a MariaDB release many years newer than anything this branch was tested against. There is currently no way to pin an older, era-appropriate version for testing.

How?

This follows #83751, which adds the same option and environment variable to trunk. This branch's wp-env keeps its configuration in packages/env/lib/config/config.js, so the change follows how phpVersion works there:

• validateConfig() checks the value (the new checkMariaDBVersion()).
• parse-config.js passes it through.
• config.js adds the default and applies WP_ENV_MARIADB_VERSION. Unlike WP_ENV_PHP_VERSION, the new variable is validated.
• build-docker-compose-config.js sets each environment's image.

New tests in packages/env/lib/config/test/config.js cover the default, root and per-environment values, the environment-variable override, and both validation errors. New tests in packages/env/test/build-docker-compose-config.js cover the image with and without a version. The config snapshot gains "mariadbVersion": null. npm run test-unit -- packages/env passes all 90 tests locally.

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]

🤖 PR meta 🤖

🏷️ Labels

This pull request needs exactly one label indicating its type, and has 0.

• Required: any label starting with [Type].
• Found: none.

Read more about Type labels in Gutenberg. If you cannot add labels yourself, a reviewer can do it for you.

[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#84410.