Release v0.20.1 - #14
Merged
Merged
Conversation
Extract initialization, block boundary, and execution handling into named helpers. Preserve queue ordering, fault behavior, IPC shapes, and coverage flushing.
…il loudly on a moved module Extensionless specifiers survive a move to a directory index, a re-export shim no longer passes the hardcoded-ecmaVersion scan vacuously, and only an isolated-vm probe failure may skip the validateSyntax cases.
… on a moved module
…ll of src/ meta_validation.js parsed with a literal ecmaVersion 2020 instead of the shared consensus constant, and the pin test only scanned metering.js and syntax.js by name. Point the parse at CONTRACT_ECMA_VERSION and have the drift test walk every .js file under src/ so a new hardcoded parse site anywhere is caught automatically.
… scan all of src/
…e sweep Generated block: do not hand-edit it. Change the tier config and re-run the tier wirer, which owns both this file and the hook so the two cannot drift. The pre-push venue gate ran the whole GitHub transcript on every push, coverage re-runs and perf scenarios included. That is the right set to grade a release with and the wrong set to pay for on every push, especially while three venues serve every repo on the platform: a long gate does not just cost its own minutes, it forms a queue behind itself for every other session pushing that hour. A push now grades the fast tier. The tiers named in the generated block move to the scheduled full sweep, which already runs against every repo every three hours and before any release or deploy, so nothing stops being graded. The verdict line is rewritten with it, which is the part that matters: a fast run can no longer print "all tiers green (same set GitHub CI runs)". It prints which tiers were deferred and states plainly that they were NOT graded there, so a fast green can never be mistaken for a full one. The dispatcher's verdict cache is keyed on repo + sha + cmd, so a fast green cannot stand in for a full one either.
…es manifests The diff job ran differential_run.js compare without ever installing node_modules, so differential.js's require of fast-check crashed the process before it could parse a single manifest. The shell loop treated that nonzero exit the same as a real consensus divergence, so every scheduled run failed with a misleading "divergence" verdict. Add the missing install step, and have the diff step distinguish a tool crash (no DIFFERENTIAL DIVERGENCE marker in the compare output) from an actual divergence verdict, so each gets its own distinct ::error:: message.
…oor and balance scoping
… compares manifests
This was referenced Sep 23, 2026
This was referenced Sep 23, 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
1 participant
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.
Release v0.20.1
Coordinated platform release across the 13-repo v0.20.1 train.
masterrelease/v0.20.1What changes
roundFloor, and balance scoping.CONTRACT_ECMA_VERSIONinmeta_validation, scans all ofsrc/, and adds code-point coverage for the toolkit gate.Sibling release PRs
Filled in by open-release-prs.sh --execute once every PR above has a number: