Skip to content

Release 1.0.6#20

Merged
firestar300 merged 8 commits intomainfrom
ver/1.0.6
Mar 26, 2026
Merged

Release 1.0.6#20
firestar300 merged 8 commits intomainfrom
ver/1.0.6

Conversation

@firestar300
Copy link
Copy Markdown
Collaborator

@firestar300 firestar300 commented Mar 26, 2026

Release 1.0.6


Note

Medium Risk
Removes the block deprecated save definition while also changing serialized markup for the close-button label, which could cause block validation issues for content saved with older versions. Remaining changes are mostly config/docs updates for the Playground demo.

Overview
Bumps the plugin/block/package versions to 1.0.6 and updates the changelogs.

Fixes the WordPress Playground blueprint.json by pointing the landing page to a deterministic demo slug, updating the installed plugin tag ref, and rewriting the demo-page creation step to use a cleaner runPHP script (with base64-encoded block content).

Updates the modal close button’s icon-only label to use a single sr-only class (instead of screen-reader-text sr-only), adds corresponding CSS, and drops the block’s deprecated definition (deprecated.js) from registration.

Written by Cursor Bugbot for commit 0d24561. This will update automatically on new commits. Configure here.

Fixes the broken PHP script in the blueprint and uses base64 encoding for the demo page content to prevent escaping issues. Updates the landing page to point directly to the newly created demo page.
…d code

Replaces the dual `screen-reader-text sr-only` classes with a localized `sr-only` class and corresponding CSS to reduce external dependencies. Removes the deprecated block version and applies general code style formatting updates across the modal components.
Updates the blockparty-modal resource reference from the 1.0.5 tag to the chore/blueprint branch to incorporate recent changes.
Adds a leading slash to the wp-load.php path to ensure the script correctly bootstraps WordPress within the Playground environment.
@firestar300 firestar300 merged commit 46e427a into main Mar 26, 2026
3 of 5 checks passed
@firestar300 firestar300 deleted the ver/1.0.6 branch March 26, 2026 14:58
Copy link
Copy Markdown

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Fix All in Cursor

Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

save,
deprecated,
} );
});
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing deprecation handler breaks v1.0.5 saved blocks

High Severity

The deprecated.js file is entirely removed and registerBlockType no longer receives a deprecated array, but the save function's output changed from 'screen-reader-text sr-only' (v1.0.5) back to 'sr-only'. Any modal blocks saved with v1.0.5 will fail WordPress block validation in the editor because the serialized HTML contains class="screen-reader-text sr-only" but the current save function now produces class="sr-only". A deprecation entry with the old v1.0.5 save markup is needed so WordPress can migrate those blocks.

Additional Locations (1)
Fix in Cursor Fix in Web

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.

1 participant