Repository navigation
Release 1.2.2 - #28
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Merged
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
Security release. Merging into
maintriggersrelease.yml, which builds and pushes the1.2.2tag from.plugin-data.release/1.2.2was branched frommain, which already contains the fix (#27, same branch as #25 ondevelop). This PR only bumps the version:mainis still at1.2.1, an existing tag, so the release workflow stopped after #27.Content
allowattribute only keeps low-risk Permissions Policy features, without origin lists;allowpaymentrequestis no longer rendered (Security: iframeallowattribute lets contributors delegate sensitive browser permissions #24).BlockRenderer, with the same filtering as the front end. Adds@wordpress/server-side-render.Version bump to 1.2.2
.plugin-datablockparty-iframe.php: header andBLOCKPARTY_IFRAME_VERSIONpackage.json/package-lock.jsonsrc/blockparty-iframe/block.jsonreadme.txt:Stable tagand changelog.wordpress-org/blueprints/blueprint.json:reflanguages/blockparty-iframe.potCHANGELOG.md:[1.2.2] - 2026-11-11, plus the missing1.2.1and1.2.2release linksTest plan
npx wp-scripts lint-js src: no errorsphpcs blockparty-iframe.php: no errorsnpm run build: compiled,build/blockparty-iframe/block.jsonreports 1.2.21.2.2does not exist yetwp-env), see fix(security): restrict iframe allow policy to low-risk features #251.2.2is created on the merge commit🤖 Generated with Claude Code
Note
Low Risk
Diff is version and documentation updates only; no application logic changes in this PR.
Overview
Release 1.2.2 — this PR aligns all release metadata and docs with the
1.2.2tag so the release workflow can publish; it does not introduce new runtime code in the diff.Version strings move from 1.2.1 to 1.2.2 in
.plugin-data,blockparty-iframe.php(header andBLOCKPARTY_IFRAME_VERSION),package.json/package-lock.json,src/blockparty-iframe/block.json,languages/blockparty-iframe.pot, WordPress.orgStable tag, and the Playground blueprint installref.CHANGELOG.mdandreadme.txtnow ship the 1.2.2 notes (iframeallowallowlisting, droppingallowpaymentrequest, server-side editor preview) and add release links for 1.2.1 and 1.2.2.Reviewed by Cursor Bugbot for commit 3563a95. Bugbot is set up for automated code reviews on this repo. Configure here.