Repository navigation
Sync accepted latest main ancestry into v3 integration - #94
Merged
Merged
Conversation
Signed-off-by: Eli Ma <eli@patch.sh>
Ivanbeethoven
merged commit Oct 8, 2026
17790ae
into
maint/mst2-native-head-with-projection
1 check failed
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
2 participants
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.
Preserve accepted upstream main ancestry in the v3 integration. The only incoming change is four documents already present on main; every incoming blob and every existing performance blob is retained exactly. No document is authored. The task diff relative to latest main remains source, necessary tests and workflows only.
Validation: independent complete recursive entry/mode/blob union, merge-tree and exact parent-delta reconstruction, and candidate whitespace passed. No Cargo, SQL, benchmark or performance execution was dispatched. Known native compile and fixture repairs remain separate. Use an ordinary merge commit with ordered parents and the exact reviewed tree. Its new GitHub signature must be valid; upstream original unknown_key history is preserved.