feat(version): merge master to 4.8.2#6817
Merged
lvs0075 merged 12 commits intoJun 3, 2026
Merged
Conversation
…,version code:18636 (tronprotocol#6542)
New workflows: - pr-build.yml: multi-OS build matrix (macOS, Ubuntu, RockyLinux, Debian11) and changed-line/overall coverage gate - pr-check.yml: PR title/body lint + Checkstyle - pr-reviewer.yml: scope-based reviewer auto-assignment - pr-cancel.yml: cancel in-progress runs when PR is closed unmerged - system-test.yml: spin up FullNode and run the system-test suite Existing workflows: - codeql.yml: bump to v4/v5 actions, switch to manual build-mode with JDK 8, add paths-ignore for docs-only changes - math-check.yml: bump checkout/upload-artifact/github-script versions
…ersion code:18643
317787106
approved these changes
Jun 3, 2026
343b4fb to
1ce9328
Compare
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.
What does this PR do?
Merge
master(now at the just-releasedGreatVoyage-v4.8.1.1) intorelease_v4.8.2.Why are these changes required?
GreatVoyage-v4.8.1.1(Hypatia) shipped onmasteras amandatory upgrade. To keeprelease_v4.8.2strictly ahead ofmaster, and to make sure the next release inherits the v4.8.1.1 fixes,masterhas to be merged forward as soon as it tags.The substantive payload is the two TVM-level edge-case fixes:
CREATE2opcode, so previously ambiguous edge cases are handled consistently.ModExpprecompiled contract.This PR has been tested by:
test(vm): add tests for create2/modExp checksmaster, this PR only carries the merge.Follow up
None.
Extra details
https://github.com/tronprotocol/java-tron/releases/tag/GreatVoyage-v4.8.1.1
-PR: merge release v4.8.1.1 to master #6811