Previously, wp-env used the WordPress version provided by Docker in the WordPress image for installations which don't specify a WordPress version. Now, wp-env will find the latest stable version on WordPress.org and check out the https://github.com/WordPress/WordPress repository at the tag matching that version. In most cases, this will match what Docker provides. The benefit is that wp-env (and WordPress.org) now controls the default WordPress version rather than Docker.
Bug Fix
Downloading a default WordPress version also resolves a bug where the wrong WordPress test files were used if no core source was specified in wp-env.json. The current trunk test files were downloaded rather than the stable version. Now, the test files will match the default stable version.
5.0.0 (2022-07-27)
Breaking Changes
Removed the WP_PHPUNIT__TESTS_CONFIG environment variable from the phpunit container. This removes automatic support for the wp-phpunit/wp-phpunit Composer package. To continue using the package, set the following two environment variables in your phpunit.xml file or similar: WP_TESTS_DIR="" and WP_PHPUNIT__TESTS_CONFIG="/wordpress-phpunit/wp-tests-config.php".
Removed the generated /var/www/html/phpunit-wp-config.php file from the environment.
Enhancement
Read WordPress' version and include the corresponding PHPUnit test files in the environment.
Set the WP_TESTS_DIR environment variable in all containers to point at the PHPUnit test files.
Bug Fix
Restrict WP_TESTS_DOMAIN constant to just hostname rather than an entire URL (e.g. it now excludes scheme, port, etc.) (#41039).
4.8.0 (2022-06-01)
Enhancement
Removed the need for quotation marks when passing options to wp-env run.
Setting a config key to null will prevent adding the constant to wp-config.php even if a default value is defined by wp-env.
4.7.0 (2022-05-18)
Enhancement
Added SSH protocol support for git sources
4.2.0 (2022-01-27)
Enhancement
Added command wp-env install-path to list the directory used for the environment.
The help entry is now shown when no subcommand is passed to wp-env.
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 merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
dependabot[bot]
commented
2 years ago
Bumps @wordpress/env from 3.0.0 to 5.1.0.
Changelog
Sourced from
@wordpress/env's changelog.... (truncated)
Commits
9b2e84achore(release): publish3a3ef19Update changelog fileseba6de6Merge changes published in the Gutenberg plugin "release/13.9" branch0315dbcchore(release): publish1faedd0Update changelog filesaf65943Merge changes published in the Gutenberg plugin "release/13.8" branchdf36728Merge changes published in the Gutenberg plugin "release/13.7" branch48d5f37chore(release): publishe829160Merge changes published in the Gutenberg plugin "release/13.5" brancha3e0b62chore(release): publishDependabot 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 merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)