chore: sync v4.1.3 release lineage - #19
Closed
zelentsov-dev wants to merge 1 commit into
Closed
Conversation
release: promote v4.1.3 to main
Owner
Author
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
Merge the immutable v4.1.3 release merge commit from main back into develop so the next protected promotion contains the current main base.
This is a graph-lineage synchronization only. The README update already present on develop remains intact.
Why
Promotion PR #18 correctly failed its lineage gate because current main commit 1ceece0 is not yet an ancestor of develop commit 5b219e8.