Skip to content

Release 1.0.6#19

Merged
firestar300 merged 7 commits intodevelopfrom
ver/1.0.6
Mar 26, 2026
Merged

Release 1.0.6#19
firestar300 merged 7 commits intodevelopfrom
ver/1.0.6

Conversation

@firestar300
Copy link
Collaborator

@firestar300 firestar300 commented Mar 26, 2026

Release 1.0.6


Note

Medium Risk
Removes the block deprecation handler and changes saved close-button markup, which could cause block validation issues for existing content created with prior versions. Playground blueprint.json changes are low risk but affect demo/install flow.

Overview
Bumps plugin and block versioning to 1.0.6 across metadata (blockparty-modal.php, package.json, block.json) and updates the changelogs.

Fixes the WordPress Playground blueprint.json by pointing landingPage to a stable demo slug, updating the installed tag ref, and rewriting the runPHP step to create that page with base64-encoded block content.

Updates the modal close-button accessibility label to use only sr-only (dropping screen-reader-text), adds matching CSS for .sr-only, and removes the deprecated.js block save definition previously used for backward-compatible validation.

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 60aaae3 into develop Mar 26, 2026
2 of 4 checks passed
@firestar300 firestar300 deleted the ver/1.0.6 branch March 26, 2026 14:58
Copy link

@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

Choose a reason for hiding this comment

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

Removing deprecated.js breaks v1.0.5 saved block content

High Severity

The deprecated.js file is deleted and the deprecated property is removed from registerBlockType, while simultaneously changing the save output from 'screen-reader-text sr-only' to 'sr-only'. Any existing posts saved with v1.0.5 have screen-reader-text sr-only in their serialized HTML, which no longer matches the current save function and has no deprecation handler to migrate it. This causes WordPress to show a "block contains unexpected or invalid content" validation error in the editor for all v1.0.5 modal 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