fix(avalanchego): per-network version defaults; Fuji needs v1.15.0-fuji - #36
Merged
Conversation
Fuji rejects stable 1.14.x nodes since the Helicon pre-release activated (0 connected peers, bootstrap never completes). Select versions per network: fuji tracks v1.15.0-fuji, mainnet stays on latest stable (v1.14.2). Pin SHA256 checksums for the new assets. subnet-evm v1.x is grafted into avalanchego releases (new asset naming, nested tarball layout, no checksums.txt), so add a grafted download path verified against pinned checksums; v0.x keeps the standalone repo path. Also compare installed version against the numeric part of the requested tag, since the binary does not report pre-release suffixes.
anishnar
approved these changes
Aug 5, 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
2 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 changed
v1.15.0-fuji(Helicon pre-release), mainnet stays on latest stable (v1.14.2, wasv1.14.1). Fuji rejects stable 1.14.x nodes since Helicon activated: fresh deploys sit at 0 connected peers and never bootstrap.v1.15.0-fujiavalanchego and subnet-evm assets (computed from the official release assets).avalanchego --versiondoes not report pre-release suffixes.Verification
ansible-playbook playbooks/l1/deploy-nodes.yml --syntax-checkpasses; defaults renderfuji => v1.15.0-fuji / v1.15.0-fujiandmainnet => v1.14.2 / v0.8.0.Open questions
v1.15.0goes stable, collapseavalanchego_fuji_versionback into the stable default and pin new checksums.