Backfill 0.11.0 release into develop - #1006
Merged
Merged
Conversation
Prepare the 0.11.0 release
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.
Summary
The 0.11.0 release was prepared on
release/0.11.0and merged tomain, then tagged and published. This brings those release commits back intodevelopso the two branches stay in sync.The diff is purely the release mechanics: the changelog entry, the regenerated translation template, and the version bumps across
edit_flow.php,package.json,package-lock.json,README.md, andAGENTS.md. There is no functional code change here —developalready contained every fix that shipped in 0.11.0; only the release-stamping commits were missing.Once merged,
developandmainpoint at identical trees.Note: the develop ruleset only permits the merge-commit method, so this should be merged with a merge commit (not squash or rebase).