Repository navigation
supernode setup: testnet download line; latest is mainnet - #13
Conversation
The page installs from releases/latest, which is now the newest mainnet release (v2.5.2 since 2026-10-08; before that a testnet build had taken it). Testnet operators get a command that picks the newest -testnet release, the same choice sn-manager makes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012joq2H25zNaTpK6yJiXZV1
There was a problem hiding this comment.
🔵 Needs a closer look
The added operator install commands depend on live external behavior (GitHub release ordering and testnet asset availability) that cannot be verified in this environment, and an incorrect build selection has real operational impact.
1 open finding
What changed in this PR
This PR updates supernodes/node-setup.mdx to fix an issue where releases/latest now resolves to the newest mainnet build (v2.5.2) rather than a testnet build. Previously, operators following the docs could unintentionally download a testnet release on mainnet (or vice versa). The change splits the Step 4 download into explicit mainnet and testnet paths and adds a one-line note for the manual "run without sn-manager" flow.
Changes:
- Step 4 now has a mainnet command (unchanged
latestURL) and a separate testnet command that resolves the newest-testnettag via the GitHub releases API. - Adds explanatory prose clarifying that
latestalways points to the newest mainnet release. - Updates the "Run the supernode binary directly" accordion to tell testnet users to replace
latest/downloadwithdownload/$TAG.
| File | Description |
|---|---|
| supernodes/node-setup.mdx | Splits the sn-manager/supernode download into mainnet and testnet variants and documents resolving the newest -testnet release tag. |
🧠 Review effort: Balanced
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
|
|
||
| Download and install the latest `sn-manager` release. Installing it under your home directory lets it update itself. | ||
|
|
||
| On **mainnet**, download the latest release: |
supernodes/node-setup.mdxinstalls fromreleases/latest. Until 2026-10-08 that wasv2.6.9-testnet, so mainnet operators got a testnet build. Nowv2.5.2is "latest", and release-kit #4 keeps testnet copies from taking it.-testnetrelease, the same choice sn-manager makes.Tested: the testnet command resolves
v2.6.9-testnet, and both file URLs answer 200. The mainnet URL redirects tov2.5.2.🤖 Generated with Claude Code
https://claude.ai/code/session_012joq2H25zNaTpK6yJiXZV1