Release AllTerrain Forms 1.1.0 - #54
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.
Prepare AllTerrain Forms 1.1.0 for WordPress.org, shipping the YAML portability and validated MIO editing features merged in #53.
Update the plugin header, version constant, npm package/lock metadata and WordPress.org stable tag together. Finalize the 1.1.0 changelog and upgrade notice, including the optional MIO Preview action and save recovery.
Validation:
npm run plugin:packagepasses (TypeScript, 463 Vitest tests and all bundles); the resulting ZIP identifies version 1.1.0 and committed bundles remain unchanged. CI also runs the full PHP suite and coding standards before merge. Publishing follows through the existing stable-tag release workflow after this PR merges.