chore: sync main ancestry before v0.5.8 promotion - #356
Merged
Conversation
release: promote v0.5.7 to main
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.
Refs #350.
Synchronizes the prior v0.5.7 promotion merge from main into development before the v0.5.8 promotion.
This branch starts at current development and adds one merge commit whose second parent is current main. Its tree is byte-for-byte identical to development (0 changed files), so it changes ancestry only and keeps the reviewed v0.5.8 release candidate intact.
This protected-PR path is needed because GitHub correctly refused a direct update of development while required checks were expected. Once current-head checks pass and this merges, #354 can be evaluated as an up-to-date development to main promotion.