Skip to content

Release 1.2.1 (back to develop) - #23

Merged
asadowski10 merged 3 commits into
developfrom
release/1.2.1
Nov 5, 2026
Merged

asadowski10 merged 3 commits into
developfrom
release/1.2.1

Conversation

@asadowski10

@asadowski10 asadowski10 commented Nov 5, 2026 •

Copy link
Copy Markdown
Member

Summary

Brings the 1.2.1 version bump back into develop, same as #18 for 1.2.0. The release itself goes through the companion PR to main.

The only differences with develop are the version bump files (.plugin-data, plugin header and constant, package.json / package-lock.json, block.json, readme.txt, blueprint, .pot) and CHANGELOG.md ([Unreleased] becomes [1.2.1]).

Test plan

  • composer cs, npx wp-scripts lint-js src, npm run build

Generated by Claude Code


Note

Low Risk
Mechanical version and changelog updates only; no functional code changes in the diff.

Overview
Syncs 1.2.1 release metadata into develop after the release to main, matching the usual post-release back-merge pattern.

Version strings move from 1.2.0 to 1.2.1 in .plugin-data, the plugin header and BLOCKPARTY_IFRAME_VERSION, package.json / lockfile, block.json, readme.txt stable tag, the .pot header, and the WordPress Playground blueprint install ref.

Release notes are finalized: CHANGELOG.md promotes [Unreleased] to [1.2.1] - 2026-11-05 (security allowlisting for iframe attributes and http/https sources, French translations, WPCS/platform bumps), and readme.txt gains a matching 1.2.1 changelog section. No block or PHP rendering logic changes appear in this diff—only versioning and documentation.

Reviewed by Cursor Bugbot for commit bc01291. Bugbot is set up for automated code reviews on this repo. Configure here.

@asadowski10
asadowski10 merged commit 17335ae into develop Nov 5, 2026
4 of 6 checks passed
@asadowski10
asadowski10 deleted the release/1.2.1 branch November 5, 2026 17:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants