chore: bump the Go toolchain to 1.26.11 for GO-2026-6859

🔎 Visual review of cb62340a: explainer, review flags and prompts to ask an AI about the change

Why

GO-2026-6859 (net/http: HTTP/1 server crash due to a MaxBytesReader header race) is fixed in go1.26.11 and reachable from thornode, including app.*THORChainApp.FinalizeBlock, openapi.HandleSwaggerUI and config.GetBootstrapPeers. The govulncheck job blocks, so every pipeline on 1.26.10 now fails in the test stage, for example !5349's pipeline 3054451017.

What

Mechanical bump of every 1.26.10 pin to 1.26.11, following 2bec99b6 (the 1.26.9 bump):

  • go.mod toolchain, .go-version, and the test/simulation/go.mod go directive
  • the .gitlab-ci.yml default image, bookworm image and dependency-proxy probe
  • build/docker/*, ci/Dockerfile.* and tools/events/Dockerfile (the golang:1.26.11, -bookworm and -alpine tags exist on Docker Hub)
  • .trunk/trunk.yaml, plus the docs and scripts that pin GOTOOLCHAIN

No dependency or code changes.

Checks

  • GOTOOLCHAIN=go1.26.11 ./scripts/govulncheck.sh: 10 reachable, 10 allowlisted, nothing outside the allowlist
  • make lint-ci: pass
  • make generate: nothing new

🤖 Generated with Claude Code

Edited by Huginn Ai

Merge request reports

Loading
Loading