Update WordPress Playground dependencies to 3.1.3#2687
Merged
Conversation
Collaborator
📊 Performance Test ResultsComparing 5629078 vs trunk site-editor
site-startup
Results are median values from multiple test runs. Legend: 🟢 Improvement (faster) | 🔴 Regression (slower) | ⚪ No change (<50ms diff) |
The install:bundle script uses --no-package-lock, which resolved electron2appx to 2.1.3 where the code was refactored, breaking the existing patch-package patch. Pinning to 2.1.2 prevents this.
epeicher
force-pushed
the
update/playground-dependencies
branch
from
7586c4d to
5629078
Compare
1 task
epeicher
commented
Mar 2, 2026
| "date-fns": "^3.3.1", | ||
| "electron-squirrel-startup": "^1.0.1", | ||
| "electron2appx": "^2.1.2", | ||
| "electron2appx": "2.1.2", |
Contributor
Author
There was a problem hiding this comment.
To prevent errors on the patch package if this version increases, more info in the commit description 5629078. The version should be updated explicitly
sejas
approved these changes
Mar 2, 2026
Member
There was a problem hiding this comment.
Upgrade looks good. Sites can be created and successfully start
Patches were applied when I run npm i:
❯ nvm use && npm i
Found '/Users/macbookpro/Documents/projects-m3.nosync/studio/.nvmrc' with version <24.13.1>
Now using node v24.13.1 (npm v11.8.0)
> postinstall
> patch-package --patch-dir apps/cli/patches && patch-package --patch-dir apps/studio/patches && node ./scripts/remove-fs-ext-other-platform-binaries.mjs && ts-node ./scripts/download-wp-server-files.ts && node ./scripts/download-available-site-translations.mjs
patch-package 8.0.1
Applying patches...
@wp-playground/wordpress@3.1.3 ✔
pm2@6.0.14 ✔
pm2-axon@4.0.1 ✔
ps-man@1.1.8 ✔
patch-package 8.0.1
Applying patches...
@automattic/generate-password@0.1.0 ✔
@types/archiver@6.0.4 ✔
@wordpress/components@32.2.0 ✔
archiver@6.0.2 ✔
electron-devtools-installer@4.0.0 ✔
electron2appx@2.1.2 ✔
sejas
pushed a commit
that referenced
this pull request
Mar 2, 2026
- Pin electron2appx to 2.1.2 to fix CI packaging failure - Update `@php-wasm/universal` from 3.1.2 to 3.1.3 - Update `@wp-playground/blueprints` from 3.1.2 to 3.1.3 - Update `@wp-playground/cli` from 3.1.2 to 3.1.3 - Update `@wp-playground/common` from 3.1.2 to 3.1.3 - Update `@wp-playground/storage` from 3.1.2 to 3.1.3 - Update `@wp-playground/wordpress` patch file for 3.1.3
1 task
1 task
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
3 participants
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.
Related issues
Proposed Changes
@php-wasm/universalfrom 3.1.2 to 3.1.3@wp-playground/blueprintsfrom 3.1.2 to 3.1.3@wp-playground/clifrom 3.1.2 to 3.1.3@wp-playground/commonfrom 3.1.2 to 3.1.3@wp-playground/storagefrom 3.1.2 to 3.1.3@wp-playground/wordpresspatch file for 3.1.3Testing Instructions
npm installand verify no errorsnpm testand verify all tests passnpm startand verify sites work correctlyPre-merge Checklist