Bump Playground and PHP-WASM packages to 3.1.29 - #3424
Closed
wojtekn wants to merge 1 commit into
Closed
Conversation
Picks up the upstream v3.1.29 release. Notable upstream changes: - @php-wasm/node exports more side-module symbols so the SQLite WASM extension can hook in (WordPress/wordpress-playground#3605). - Personal WP blueprint drops the fake browser chrome and improves dependent tab handling (#3601). - The PHP-WASM build now excludes unused dependencies when generating package.json (#3232), which collapses several layers of duplicated transitive deps in our lockfile. All Playground/PHP-WASM packages remain pinned to exact versions, per AGENTS.md.
Contributor
Author
|
The huge line count change comes from WordPress/wordpress-playground#3232 |
Contributor
Author
|
Closing in favor of #3496 |
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.
Related issues
How AI was used in this PR
Claude Code located every
@wp-playground/*/@php-wasm/*dependency, performed the version bump, regeneratedpackage-lock.json, and ran the verification workflow (typecheck, tests, CLI build, CLI smoke test). I reviewed the lockfile delta and the upstream changelog before pushing.Proposed Changes
@wp-playground/*and@php-wasm/*packages from 3.1.28 → 3.1.29 acrossapps/cli,apps/studio,apps/ui,tools/common, andtools/benchmark-site-editor. All versions remain pinned exactly (no^/~), per AGENTS.md.package-lock.json. The lockfile shrinks by ~1.5k lines because upstream PR WordPress/wordpress-playground#3232 trimmed unused dependencies from the per-PHP-version@php-wasm/node-*packages, so npm no longer needs to nest duplicate copies ofajv,ws,ini, etc. under each of them.Notable upstream changes in v3.1.29:
package.jsonfiles (#3232)No breaking changes documented upstream.
Testing Instructions
Automated checks already run locally on this branch:
npm run typecheck— all workspaces pass.npm test— 1575/1576 pass. The one failure (apps/cli/remote-session/tests/daemon.test.ts > startDaemon / stopDaemon) is a pre-existing timing flake unrelated to Playground; it passes cleanly when re-run in isolation.npm run cli:build— succeeds.node apps/cli/dist/cli/main.mjs site create --help— CLI boots and lists Playground-backed PHP versions (7.4 – 8.5).Manual smoke test for reviewers:
npm installto refresh the lockfile.npm startand create a new local site (any PHP / WP version).Pre-merge Checklist