Update dependency @wordpress/env to v11

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@wordpress/env (source)	10.31.0 → 11.17.0

---

Release Notes

WordPress/gutenberg (@​wordpress/env)

v11.17.0

Compare Source

New Features

• Add a mariadbVersion option and WP_ENV_MARIADB_VERSION environment variable to choose the MariaDB version used by the Docker runtime, including versions older than 10.4 (#​83751).
• Explain why wp-env start fails when a database was last used by a newer MariaDB version, which MariaDB cannot downgrade from (#​83751).
• Stop wp-env start with an error naming the image when an image cannot be pulled and is not available locally, such as a mariadbVersion that does not exist, instead of reporting that cached images will be used (#​83751).
• Make wp db commands, and so wp-env reset, work with a mariadbVersion older than 11.4. The MariaDB client in the CLI image requires TLS, which those servers do not offer, so the CLI image now runs the client without verifying the server certificate, as WP-CLI does from db-command 3.0 (#​83751).

Bug Fixes

• Reject a phpVersion or WP_ENV_PHP_VERSION that is not only a version number, such as 8.2-apache or abc8, instead of failing later because the Docker image does not exist (#​83751).
• Pass -T to docker compose exec when stdin is not a terminal, so commands run from a Git hook, which has a TTY on stdout but not on stdin, no longer fail with "cannot attach stdin to a TTY-enabled container" (#​78374).

Internal

• Update @wp-playground/cli to 3.1.56, which replaces the fs-ext optional dependency, compiled with node-gyp at install time, with fs-ext-extra-prebuilt, which ships prebuilt binaries and works without running install scripts (#​84012).
• Update simple-git to v4, which has better TypeScript support (#​84137).

v11.16.0

Compare Source

Bug Fixes

• Wait for lifecycle script output streams to close before reporting command failures, so their error output is not lost (#​82735).

v11.15.0

Compare Source

Bug Fixes

• Point the apt sources of the bullseye-based WordPress images (PHP 7.4 and 8.0) at archive.debian.org, so building them no longer fails now that Debian 11 has reached end-of-life and left the regular mirrors (#​82478).

v11.14.0

Compare Source

Bug Fixes

• Update git sources to the latest commit when --update is passed. Previously, a source pointing at a branch (such as "core": "WordPress/WordPress") stayed at the commit it was first cloned at, no matter how many times it was updated.
• Do not fail wp-env start when Docker images cannot be pulled (e.g., the Docker registry is unreachable); fall back to locally cached images and show a notice instead. (#​81631)

v11.13.0

Compare Source

v11.12.0

Compare Source

v11.11.0

Compare Source

v11.10.0

Compare Source

v11.9.0

Compare Source

v11.8.1

Compare Source

v11.8.0

Compare Source

Enhancements

• Use partial clones (--filter=blob:none) when downloading git sources and the PHPUnit test suite to reduce download size. (#​78918)

Bug Fixes

• Replace extract-zip with adm-zip to fix silent hang on Node 24.16.0 (libuv 1.52.1) when downloading URL-based zip sources. (#​78762)

v11.7.0

Compare Source

v11.6.0

Compare Source

v11.5.0

Compare Source

v11.4.0

Compare Source

Bug Fixes

• Fix WP-Cron, REST API loopback, and Site Health loopback failures when wp-env runs on a non-default port. Apache inside the WordPress container now also listens on the host-mapped port, so PHP loopback requests to WP_HOME succeed instead of being refused. (#​20569)

v11.3.0

Compare Source

v11.2.0

Compare Source

v11.1.0

Compare Source

Bug Fixes

• Suppress spinner and success message output when using --json flag to ensure clean, parseable JSON output.

v11.0.1

Compare Source

v11.0.0

Compare Source

Bug Fixes

• Playground runtime now supports zip archive themes, matching Docker runtime behavior. (#​75140).
• Add MySQL healthcheck to prevent race condition where WordPress containers start before MySQL is fully initialized. Uses MariaDB's official healthcheck.sh script with MARIADB_AUTO_UPGRADE to support both new and existing installations.
• Remove non-functional WP_ENV_MULTISITE config.

New Features

• Added --auto-port flag to the start command. When passed, wp-env automatically finds available ports if the configured ports are busy. Without this flag, ports default to 8888/8889 and Docker reports an error if they are busy (matching pre-existing behavior).

Breaking Changes

• Pretty permalinks (/%year%/%monthnum%/%day%/%postname%/) are now enabled by default, matching WordPress core behavior on fresh installs. Previously, plain permalinks were used because the loopback test that WordPress runs during installation fails inside Docker.
• The port option now defaults to null (auto-select) instead of 8888. When null, wp-env tries port 8888 (or 8889 for tests) first, then falls back to an available ephemeral port. Set an explicit port number to preserve the previous behavior.
• Replaced install-path command with status command. The work directory path is now available as part of the status output.

New Features

• Added phpmyadmin boolean configuration option to enable phpMyAdmin. Setting phpmyadminPort also enables phpMyAdmin for backward compatibility.
• Added phpMyAdmin support to the Playground runtime. When enabled, phpMyAdmin is available at http://localhost:<port>/phpmyadmin.
• Added status command that shows comprehensive environment information including running state, URLs, ports, configuration, and paths.
• Added --config global option to specify a custom configuration file path, enabling multiple parallel environments from the same directory.
• Added testsEnvironment configuration option. Set to false to skip creating test containers (tests-mysql, tests-wordpress, tests-cli, tests-phpmyadmin), reducing resource usage when test isolation is achieved via separate config files.

v10.39.0

Compare Source

New Features

• Add experimental WordPress Playground runtime support. Use --runtime=playground flag to start wp-env with Playground instead of Docker.
• Add cleanup command to remove environment-specific resources (containers, volumes, networks, and local files) while preserving Docker images for faster re-starts.
• Add --force flag to both destroy and cleanup commands to skip the confirmation prompt.
• Rename clean command to reset for clarity. The clean command is now deprecated but still works as an alias.

Deprecation

• The clean command is deprecated. Use reset instead. The afterClean lifecycle script is also deprecated in favor of afterReset.

v10.38.0

Compare Source

v10.37.0

Compare Source

v10.36.0

Compare Source

v10.35.0

Compare Source

v10.34.0

Compare Source

v10.33.1

Compare Source

v10.33.0

Compare Source

v10.32.0

Compare Source

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

• Configuration used: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: dd75e93f-020c-44a6-a508-9508a88d6964

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}