chore: sync main release ancestry into development - #396
Merged
Conversation
release: promote v0.5.8 to main
release: promote v1.0.0 to main
12 tasks
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.
Summary
Merge the prior protected
mainrelease ancestry intodevelopmentwithout changing thedevelopmenttree.Promotion PR #395 is correctly
development->main, but strict branch protection reportsdevelopmentas behind because the earlier v1.0.0 promotion merge (51907b6) is not an ancestor of the ongoing development line. This merge commit has parents:development:7b3bc866b08c367700827c5b7f358640775f5d58main:51907b6f87e7e3b9108d5c7d019064f081425bd4git diff HEAD^1..HEAD --name-onlyis empty: this changes ancestry only and preserves the already-validated v1.1.0 release tree exactly.Tracks release #393. After this PR passes current-head CI and required review, merging it will refresh #395 on an up-to-date
developmenthead.Validation
7b3bc866.