chore: sync main ancestry before v0.5.8 promotion - #355
Closed
mohanagy wants to merge 1 commit into
Closed
Conversation
release: promote v0.5.7 to main
Owner
Author
|
Superseded by #356. Using main directly as the head remained behind protected development, so strict branch protection could not merge it. #356 starts from current development and adds current main as a second parent with an identical tree, enabling the ancestry sync through normal protected checks. |
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
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.
Refs #350.
Synchronizes the prior v0.5.7 promotion merge from main back into development before the v0.5.8 promotion.
This is an ancestry-only maintenance sync: main contributes its prior promotion merge commit, while development retains the already-reviewed v0.5.8 tree. It is required because strict branch protection will not update the protected development branch directly while required checks are expected.
After this merges with current-head checks, #354 can be re-evaluated as an up-to-date development to main promotion.