Repository navigation
Conversation
| { | ||
| "app-latest-tag": "v10.5.0", | ||
| "app-latest-sha": "6013e758d5dceb75827ad191c8d739d7c43cfa04", | ||
| "app-latest-tag": "v10.6.0", |
There was a problem hiding this comment.
🟡 Mainnet source build uses outdated Go
After app-latest-tag advances to v10.6.0, environment setup still installs Go 1.26.8. That release requires Go 1.26.10, so offline builds fail and online builds require an unadvertised toolchain download.
Learn more
The Mainnet Beta version constant feeds the source-install instructions, which set ver to golangNodeMainnet from general constants. Those constants remain at Go 1.26.8. The v10.6.0 upstream go.mod declares go 1.26.10, so that installed compiler does not meet the release requirement. Go's automatic toolchain selection can hide the mismatch online, but it cannot fetch a newer toolchain offline or with GOTOOLCHAIN=local.
Example: An operator follows the Mainnet Beta setup and installs Go 1.26.8, then checks out v10.6.0 and runs GOTOOLCHAIN=local make install. Go rejects the module's 1.26.10 requirement instead of building the binary.
Recommended fix: Update golangNodeMainnet in constants/general.json to at least 1.26.10 when selecting this app release, and verify that it also satisfies the selected celestia-node release.
Was this helpful? React with 👍 or 👎 to provide feedback.
8f7783c to
23fc003
Compare
23fc003 to
a8938cf
Compare
Proposes newer releases for mainnet using numeric major/minor/patch ordering.
Includes matching Node API specs, Mainnet Beta celestia-app OpenAPI, and generated skill links. Repairs API version drift even without a new release.
OpenAPI is generated from the exact Mainnet Beta app tag and commit in the docs constants, including during Mocha updates.
Mainnet uses stable releases; Mocha uses only
-mochareleases.Review upstream release notes and network compatibility before merging, especially for major/minor upgrades. A published binary does not establish network activation.