Merge develop into release_0.8.31 - #152
Merged
CodeNinjaEvan merged 53 commits intoAug 19, 2026
Merged
Conversation
Release 0.8.29
…and copy) Co-authored-by: Daniel Kirchner <daniel@ekpyron.org> Co-authored-by: clonker <1685266+clonker@users.noreply.github.com> Co-authored-by: Kamil Śliwak <kamil.sliwak@codepoets.it> (cherry picked from commit 2ab47bd)
Co-authored-by: Daniel Kirchner <daniel@ekpyron.org> Co-authored-by: Kamil Śliwak <kamil.sliwak@codepoets.it> (cherry picked from commit 44cdd8d)
…cy and via-ir on deletion, partial assigments and copy Co-authored-by: Daniel Kirchner <daniel@ekpyron.org> Co-authored-by: Kamil Śliwak <kamil.sliwak@codepoets.it> (cherry picked from commit 0495910)
(cherry picked from commit d38b746)
(cherry picked from commit c4dd9e4)
(cherry picked from commit 0983a90)
(cherry picked from commit a0a3dd8)
(cherry picked from commit 139d696)
Use Tarjan's strongly-connected-components algorithm: a function is recursive iff it lies in a non-trivial SCC or has a self-edge. Also add intersection recursive cycles regression test to function specializer tests. (cherry picked from commit 5025618)
These are tests to demonstrate incorrect processing of inheritance hierarchy in the presence of custom storage layout close to the storage end. (cherry picked from commit 2ac7929)
When the compiler emits a warning about storage base location being too close to storage end, it calls a helper function to determine the last storage variable. This helper function previously unintentionally reversed the linearized based contracts annotation. The function only needs to take reversed **view**. It should not modify the underlying data. (cherry picked from commit 9fb715d)
(cherry picked from commit 58bc9f8)
(cherry picked from commit 56edc07)
…nHandle` to utilities (cherry picked from commit 47e36a3)
(cherry picked from commit 422fe84)
…ambiguated (cherry picked from commit d32ee36)
(cherry picked from commit 11815d2)
…-to-sol-2026-3-0830 Backport SOL-2025-1 through SOL-2026-3 fixes to release_0.8.30
…e-updates-0830 Backport release_0.8.31 build pipeline updates to release_0.8.30
…d-workspace ci: isolate S3 upload workspace
The pre-tangerine-whistle fallback paths in both code generators still derived the retained-gas amount from Ethereum fork-dependent GasCosts::callGas(). Switch them to the fixed TVM price for consistency with the GasMeter alignment. Also add GasMeter unit coverage for the SELFDESTRUCT estimate (tvmSelfdestructGas + callNewAccountGas).
…gasmeter-tvm-pricing fix(evmasm): align gas estimates with TVM pricing
…runtime-correctness fix: align TRON runtime and compiler semantics
…abi-api-compatibility fix: clarify TRON builtin parameter names
…input-path-hardening fix: harden compiler inputs and avoid root LSP scans
- Mark SOL-2025-1, SOL-2026-1, SOL-2026-2 and SOL-2026-3 as fixed in 0.8.30 on this release line: the fixes were backported from upstream 0.8.32/0.8.34/0.8.36, so the bug list must not claim 0.8.30 is still affected. - Restore TRON terminology (Trx) in legacy bug descriptions that were inadvertently overwritten with upstream wording (Ether) by the cherry-picks. - Regenerate docs/bugs_by_version.json from docs/bugs.json and this branch's Changelog.md; entries for versions not released on this branch (0.8.31+) drop out accordingly.
…bugs-doc-metadata docs: fix bug metadata for TRON 0.8.30 security backports + fix: reject Ethereum units in AST imports
…smt-json-gasmeter-hardening fix: harden SMT, JSON input, and TVM gas estimation
Release 0.8.30
# Conflicts: # .github/workflows/build.yml # docs/bugs.json
|
Thank you for your contribution to the Solidity compiler! A team member will follow up shortly. If you haven't read our contributing guidelines and our review checklist before, please do it now, this makes the reviewing process and accepting your contribution smoother. If you have any questions or need our help, feel free to post them in the PR or talk to us directly on the #solidity-dev channel on Matrix. |
yanghang8612
marked this pull request as ready for review
August 19, 2026 10:00
CodeNinjaEvan
approved these changes
Aug 19, 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
6 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.
Summary
developstate for TRON Solidity 0.8.30 intorelease_0.8.31Conflict resolutions
RUNNER_TEMPworkspace used by the S3 artifact packaging/upload jobValidation
git diff --checkpasseddocs/bugs.jsonanddocs/bugs_by_version.jsonpassed JSON validationscripts/regressions.py,scripts/splitSources.py, andtest/lsp.pypassed Python syntax compilation.github/workflows/build.ymlparsed as YAMLbash -nrelease_0.8.31@03423cbanddevelop@343938eas parentsThe optional local compiler smoke build could not start because GitHub submodule downloads repeatedly failed with a local LibreSSL connection error. Full multi-platform CI is triggered by the pushed branch.