Keep the Playground demo safe without zstd - #756
Merged
Conversation
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
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.
Summary
.figintake with an actionable 501latest, independently of optional extension build/runtime proofThis advances #656 without claiming its optional zstd acceptance is complete. Figma can be re-enabled in hosted Playground after WordPress/wordpress-playground#4108 is merged and deployed; the canonical demo no longer depends on that timeline.
Verification
npm test(all suites passed except the publication assertion changed by this PR; that assertion was updated and rerun successfully)npm run test:php-wasm-zstdphp tests/smoke-importer-block.php(339 assertions)php -n tests/figma-zstd-decoder.php nativephp -n tests/figma-zstd-decoder.php commandphp -n tests/figma-zstd-decoder.php unavailablephp -n -d disable_functions=proc_open tests/figma-zstd-decoder.php disabledactionlint .github/workflows/release-php-wasm-zstd.ymlgit diff --checkFollow-up
A new Homeboy release is required after merge so the release-tagged safe blueprint can be published to
playground/latest/blueprint.json; until then the current README alias remains absent.AI assistance
OpenAI
openai/gpt-5.6-solvia OpenCode diagnosed the publication/runtime coupling, implemented the safe capability and publication boundaries, added regression coverage, and ran verification. Chris Huber reviewed and owns the change.