npm(deps-dev): bump @wordpress/env from 10.39.0 to 11.0.0 in the dev-dependencies group

[dependabot]

Bumps the dev-dependencies group with 1 update: @wordpress/env.

Updates @wordpress/env from 10.39.0 to 11.0.0

Changelog

Sourced from @​wordpress/env's changelog.

11.0.0 (2026-02-18)

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.

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.
• 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.

Commits

• 376124a chore(release): publish
• c5b9f23 Update changelog files
• 4416c63 Merge changes published in the Gutenberg plugin "release/22.6" branch
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions