feat(version): merge master to 4.8.3 - #7010
Merged
Merged
Conversation
* feat(vm): add optimized storage layout and alias write checks * feat(api): separate outbound JSON parsing * perf(vm): cache alias check at Storage construction --------- Co-authored-by: halibobo1205 <halibobo1205@gmail.com>
…,version code:18830 (#7008)
halibobo1205
requested review from
317787106,
CodeNinjaEvan,
lvs0075 and
yanghang8612
October 1, 2026 09:58
317787106
approved these changes
Oct 1, 2026
lvs0075
approved these changes
Oct 1, 2026
yanghang8612
approved these changes
Oct 1, 2026
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
4 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.
What does this PR do?
Merge
master(now at the just-releasedGreatVoyage-v4.8.2.3) intorelease_v4.8.3.Why are these changes required?
GreatVoyage-v4.8.2.3(Anaxagoras) shipped onmasteras amandatory upgrade. To keeprelease_v4.8.3strictly ahead ofmaster, and to make sure the next release inherits thev4.8.2.3fixes,masterhas to be merged forward as soon as it is tagged.Follow up
None.
Extra details