Skip to content

docs: align Go version in README and CONTRIBUTING with go.mod (1.26.3)#125

Open
abhicris wants to merge 1 commit into
luxfi:mainfrom
abhicris:kcolb/fix-2026-06-01-go-version-docs
Open

docs: align Go version in README and CONTRIBUTING with go.mod (1.26.3)#125
abhicris wants to merge 1 commit into
luxfi:mainfrom
abhicris:kcolb/fix-2026-06-01-go-version-docs

Conversation

@abhicris
Copy link
Copy Markdown

@abhicris abhicris commented Jun 1, 2026

Why

The docs disagree with each other and with go.mod about the minimum Go toolchain. A new contributor who follows the README badge installs Go 1.21.12, hits the prerequisites line that says 1.23.9, and then go build fails because go.mod declares go 1.26.3. Fixing this saves the first-build friction.

What changed

  • README.md badge: 1.21.12 to 1.26.3
  • README.md "Building From Source" prerequisite: >= 1.23.9 to >= 1.26.3
  • CONTRIBUTING.md top-of-file prerequisite: >= 1.23.9 to >= 1.26.3
  • CONTRIBUTING.md "Prerequisites" section: 1.21.12 or higher to 1.26.3 or higher

Source of truth: go.mod line 10 (go 1.26.3). Dockerfile ARG is 1.26.1 which already builds against the same toolchain line.

What didn't change

  • No code, no go.mod / go.sum, no workflows, no lockfiles.
  • Other Go-version mentions inside HISTORY.md / RELEASES.md are left alone since they describe historical releases.

README badge and prerequisites listed Go 1.21.12 / 1.23.9 in different
places, but go.mod requires Go 1.26.3. Bring the docs in sync so new
contributors install a toolchain that can actually build the node.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant