Pin @wordpress/env to unblock the e2e install - #119
Merged
Merged
Conversation
@wordpress/env 10.39.0 added a dependency on @wp-playground/cli, which pulls @php-wasm/node 3.1.55, which in turn depends on @php-wasm/node-8-1. That package is not published on npm, so yarn cannot resolve it and the e2e job dies during install before a single test runs. packages/join-e2e had @wordpress/env at ^10.0.0 and no yarn.lock of its own, so CI floated onto 10.39.0 as soon as it was released. The last green e2e run was 4 September, before that version shipped. Pinned to ~10.38.0, the last line that does not reach @wp-playground. Worth revisiting once upstream publish node-8-1 or drop the reference. This matters beyond CI noise: release-plugin.yml has the WordPress.org deploy job gated on e2e, so nothing can be released until it resolves. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The e2e job installs with npm ci, which refuses to run when the lock file disagrees with package.json. Pinning the dependency without regenerating the lock swapped one install failure for another. Lock now resolves @wordpress/env to 10.38.0 and no longer reaches @php-wasm/node-8-1. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The e2e job has been failing during
yarn install, before any test runs. Not a test failure and nothing to do with any open PR.Cause
@wordpress/env10.39.0 added a dependency on@wp-playground/cli, which pulls@php-wasm/node3.1.55, which depends on@php-wasm/node-8-1. That package is not published on npm at any version, so yarn cannot resolve it and the install dies.packages/join-e2ehad@wordpress/envat^10.0.0with no yarn.lock of its own, so CI floated onto 10.39.0 the moment it was released. Last green e2e run was 4 September, before that version shipped.Fix
Pin to
~10.38.0, the last line that does not reach@wp-playground. Verified resolving cleanly. Worth unpinning once upstream publishnode-8-1or drop the reference.Why this is urgent rather than housekeeping
release-plugin.ymlgates the WordPress.org deploy job onneeds: [php-tests, jest-tests, e2e]. While e2e cannot install, no version of the plugin can be released at all.🤖 Generated with Claude Code