eba9361cb8
* update wp-env package * bump versions in e2e workflows * Fix job names * explicitly set core WP version without this, the `mappings` configuration option causes breakage due to what appears to be a bug in the package. * Change how GB install job is setup `wp-env` currently has an issue where if you define the explicit WP version to install (vs just what is included by default), permissions aren’t configured correctly for the WP folder in the containers. So the ability to install plugins via cli is not possible. This only surfaces in linux environments. I tried a number of ways to work around this but in the end the only foolproof way is to configure the environment to be setup with the installed plugin. |
||
|---|---|---|
| .. | ||
| ISSUE_TEMPLATE | ||
| workflows | ||
| CODEOWNERS | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| SECURITY.md | ||
| config.yml | ||
| label-sync-config.json | ||
| patch-initial-checklist.md | ||
| patch-release-pull-request.md | ||
| pull_request_template.md | ||
| release-automation-config.json | ||
| release-initial-checklist.md | ||
| release-pull-request.md | ||