Merged
Conversation
chore: release 1.1.1
Pins the WordPress Playground blueprint plugin data to the 1.1.1 tag instead of the main branch.
Updates the Setup Node.js action to source the version from package.json instead of a hardcoded value. This ensures consistency across environments and simplifies version management.
Adds a must-use plugin to the blueprint that filters `wp_kses_allowed_html` to permit iframes. This ensures the demo page content isn't stripped of its iframe elements by WordPress's security filters.
Renames the must-use plugin file responsible for filtering allowed HTML tags in the Playground environment. While the filename now mentions SVG, the current implementation continues to permit iframe tags to ensure demo content renders correctly.
Updates the KSES mu-plugin to permit the 'loading' attribute on iframe tags. This ensures that lazy-loading attributes on iframes are not stripped by WordPress security filters in the Playground environment.
Replaces the array-based string construction with a nowdoc to improve readability and maintainability. This also cleans up the allowed iframe attributes list, removing a duplicate "id" entry and fixing the string formatting for the "loading" attribute.
Renames the must-use plugin file from `blockparty-iframe-playground-svg-kses.php` to `blockparty-iframe-playground-kses.php`. This corrects a naming inconsistency as the plugin currently handles iframe permissions rather than SVG tags.
fix(blueprint): allow iframe tags in playground content
Removes Psalm and its WordPress plugin from development dependencies, scripts, and GrumPHP configuration. The associated psalm.xml.dist configuration file has also been deleted as the project moves away from this tool for static analysis.
chore: remove psalm static analysis
Bump version across all configuration files and update the WordPress.org Playground blueprint. This release fixes a potential fatal error in the Playground by using a nowdoc for the mu-plugin generation, ensuring the iframe allowlist PHP is syntactically valid.
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.
Bump version across all configuration files and update the WordPress.org Playground blueprint.
This release fixes a potential fatal error in the Playground by using a nowdoc for the mu-plugin generation, ensuring the iframe allowlist PHP is syntactically valid.