Skip to content

chore(deps): bump Go toolchain to 1.26.9 (GO-2026-6617) - #3141

Closed
gchahcg wants to merge 1 commit into
vavallee:mainfrom
gchahcg:chore/bump-go-toolchain-1.26.9
Closed

gchahcg wants to merge 1 commit into
vavallee:mainfrom
gchahcg:chore/bump-go-toolchain-1.26.9

Conversation

@gchahcg

@gchahcg gchahcg commented Oct 11, 2026

Copy link
Copy Markdown
Contributor

Summary

GO-2026-6617 (HTTP/2 server crash from an HPACK encoder race in net/http), fixed in go1.26.9, landed at HIGH severity in both govulncheck's and Grype's vulnerability databases today. The repo's pinned go1.26.8 toolchain is affected, which fails the lint job's govulncheck step and the Container Scan job's Grype scan on every open PR right now, and will fail on main's own next CI run too — I hit this on an unrelated PR (#2915) and it's not specific to that diff: main's go.mod carries the identical pin.

Urgent and small on purpose: this blocks CI repo-wide until it merges.

What changed

Every build target that names a Go version moves together, per make go-version-check (the discipline #2956 established):

  • go.mod: toolchain go1.26.8 → go1.26.9
  • Dockerfile, cmd/discord-stats/Dockerfile, cmd/telemetry-server/Dockerfile: golang:1.26.8-alpine → golang:1.26.9-alpine, digest updated to the real manifest digest for that tag (fetched from the registry and cross-checked: the same method reproduces the existing 1.26.8 pin's known-correct digest byte for byte)
  • Every setup-go go-version in .github/workflows/{ci,canary,fuzz,ping-drift,security}.yml (14 occurrences): "1.26.8" → "1.26.9"
  • docs/ARCHITECTURE.md: mentions the pinned tag, updated to match

Checklist

  • Tests added or updated — no behaviour change; existing suite re-verified against the new toolchain
  • Doc-update gate cleared — docs/ARCHITECTURE.md
  • Wiki pages updated if user-facing behaviour changed — n/a, no user-facing change
  • Changelog fragment added — changelog.d/go-toolchain-1.26.9-cve.md

Test plan

  • make go-version-check — passes (Go 1.26.9 everywhere: go.mod, 3 Dockerfiles, 18 workflows)
  • govulncheck ./... — clean (was reporting GO-2026-6617 before the bump)
  • go test ./cmd/... ./internal/... — full suite passes on go1.26.9
  • golangci-lint run (v2.11.4) — 0 issues
  • docker build -f Dockerfile . — succeeds end to end on the new base image
  • Verified the new Dockerfile digest resolves with docker pull golang:1.26.9-alpine@sha256:...

🤖 Generated with Claude Code

https://claude.ai/code/session_01WA2CUNg5o4wUBaX6yWXNNk

GO-2026-6617 (HTTP/2 server crash from an HPACK encoder race in
net/http) lands at HIGH severity in both govulncheck's and Grype's
vulnerability databases as of today, both freshly updated; it is fixed
in go1.26.9. The repo's pinned go1.26.8 toolchain is affected, which
fails the lint job's govulncheck step and the container image's Grype
scan on every PR and on main's own next run, starting now.

Bumps go.mod's toolchain directive, all three Dockerfiles' golang base
image (tag and digest, verified against the real registry manifest and
a full docker build), and every workflow's setup-go go-version, kept in
lockstep per make go-version-check (vavallee#2956's discipline). docs/ARCHITECTURE.md
mentions the pinned tag and is updated to match.

Verified: make go-version-check passes, govulncheck ./... is clean,
full Go test suite passes, golangci-lint v2.11.4 is clean, and a full
docker build -f Dockerfile . succeeds end to end.

Signed-off-by: gch ahcg <gchahcg@proton.me>
@github-actions github-actions Bot added the bindery-notified Discord notification already sent for this PR label Oct 11, 2026
@codecov

codecov Bot commented Oct 11, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@vavallee

Copy link
Copy Markdown
Owner

Thanks for catching this so quickly. #3131 had the same Go 1.26.9 bump and landed first, so I'm closing this one to avoid a duplicate.

@vavallee vavallee closed this Oct 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bindery-notified Discord notification already sent for this PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants