Release v0.20.0 - #16
Merged
Merged
Conversation
Both entries (src/consensus_rules_digest.js, src/db/index.js) were copied verbatim out of xchain-indexer's twin and never adapted; this repo has neither file, so the walk applied them zero times while the summary still reported declared dynamic edges: 2, confidence the tool had not earned. DYNAMIC_EDGES is now empty (grep confirms no computed require exists under src/), and a new assertDynamicEdgesResolve check fails loudly, by name, if a future declaration's `from` is not in the tracked tree, instead of passing silently as one of N declared. Also fixes a one-line comment drift against the xchain-regtest-miner twin so the two vendored copies read byte-identical again. Row 78/79 path-resolution sweep.
This was referenced Sep 17, 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.
Title: Release v0.20.0
Summary
Fixed
Sibling release PRs
Merge order
Merge order: merge after xchain-vm, in any order with xchain-decoder, xchain-sync, xchain-utxo-tracker, xchain-regtest-miner, and before xchain-indexer.
CI note
GitHub CI on this branch clones sibling repos at develop, not at this release branch, unless a workflow call passes siblings-ref for release branches. A cross-repo guard failure here can reflect that develop-only comparison rather than a real disagreement with a sibling still on this release branch; check the venue pre-push gate (which ships each companion at its own release branch) before treating a red guard as a defect.