chore: advance Lotus Next transport and realtime foundation pointer (#163) - #164
Merged
Conversation
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
lotus-nextgitlink from the previously reviewed foundation at56db603f28b1244c989d8e40b997418b37fbc562to current Lotus Nextmain@b0bc55f63d786e01c902984835218f7789e3b0cb.Closes #163
Parent migration tracker: bigduu/lotus-next#11
Submodule Updates
lotus-next56db603f28b1244c989d8e40b997418b37fbc562b0bc55f63d786e01c902984835218f7789e3b0cb40dac3f) and epoch-safe half-open WSS recovery (b0bc55f). The diff is intentionally one pointer even though the upstream range contains both accepted commits; no intermediate root pin is needed.Verification
origin/main@001727fd7b4227c93e0edc4b45b52f015e8d50f1.git diff --cached --rawbefore commit showed exactly one mode-160000update:lotus-next 56db603 -> b0bc55f.git diff --check origin/main...HEADpassed.bigduu/lotus-nextmain@b0bc55f63d786e01c902984835218f7789e3b0cb.eaaf10aand PR chore: bump bamboo permission policy pointer #23 exact headc4ca62cboth received independent APPROVE results and exact-head Node 22/24 success before merge; Issues docs: allow agent merges after live gates #20 and chore: bump bamboo permission config foundation #22 are closed and Roadmap Done.Test Plan
git diff --check origin/main...HEADgit diff --raw origin/main...HEADgit diff --name-only origin/main...HEADgit ls-tree HEAD lotus-nextorigin/maingitlink remains byte-for-byte unchanged.Screenshots
Not applicable; root repository gitlink-only change.