add blueprint bump version - #44
Merged
Merged
Conversation
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.
Note
Low Risk
Release-only tooling and packaging metadata; no runtime plugin behavior changes.
Overview
Release bumps now keep the WordPress Playground blueprint in sync with the new semver by updating the git install step’s
refin.wordpress-org/blueprints/blueprint.json(same tag the rest of the release uses).scripts/bump-version.jsregisters that blueprint path, addsbumpBlueprint(), and runs it frommain()after readme/changelog updates..gitattributesadds/scripts/toexport-ignoreso release archives omit internal tooling.Reviewed by Cursor Bugbot for commit 829c682. Bugbot is set up for automated code reviews on this repo. Configure here.