Loading
chore: bump the Go toolchain to 1.26.11 for GO-2026-6859
🔎 Visual review ofcb62340a: 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.modtoolchain,.go-version, and thetest/simulation/go.modgo directive- the
.gitlab-ci.ymldefault image, bookworm image and dependency-proxy probe build/docker/*,ci/Dockerfile.*andtools/events/Dockerfile(thegolang:1.26.11,-bookwormand-alpinetags exist on Docker Hub).trunk/trunk.yaml, plus the docs and scripts that pinGOTOOLCHAIN
No dependency or code changes.
Checks
GOTOOLCHAIN=go1.26.11 ./scripts/govulncheck.sh: 10 reachable, 10 allowlisted, nothing outside the allowlistmake lint-ci: passmake generate: nothing new
Edited by Huginn Ai