Skip to content

Build and test with Go 1.26.10 - #34

Merged
thrawn01 merged 1 commit into
mainfrom
thrawn01/eng-584-build-and-test-with-go-12610
Oct 29, 2026
Merged

thrawn01 merged 1 commit into
mainfrom
thrawn01/eng-584-build-and-test-with-go-12610

Conversation

@thrawn01

Copy link
Copy Markdown
Contributor

Purpose

Go releases before 1.26.10 accept certificate chains signed through eight compromised eMudhra intermediate CAs (CVE-2026-111943 / GO-2026-6809). groupcache-go's HTTP transport verifies peers over TLS when a TLS config is set, so callers inherit the hole from the Go they build with. This moves the module and its CI to the fixed Go.

Importers now need Go 1.26.10 or later, which the user chose for this ticket, as for gubernator in ENG-578.

-go 1.24.0
+go 1.26.10

Implementation

  • go.mod: go line raised to 1.26.10. go mod tidy leaves go.sum unchanged.
  • CI workflow: dropped the 1.24.x matrix (one OS, one version) and set go-version-file: go.mod, so CI tracks the module's minimum.
  • golangci-lint pinned to v2.15.0 in both the workflow (was v2.6.1) and the Makefile (was v1.61.0, a v1 release; the repo has no lint config, so v2 defaults apply).
  • transport/mock_transport.go: v2.15.0 reports staticcheck QF1012 on WriteString(fmt.Sprintf(...)), so it is now fmt.Fprintf. Same output.

Verification

Ran with GOTOOLCHAIN=go1.26.10: go mod tidy (no diff beyond go.mod), go vet ./..., golangci-lint run ./... (golangci-lint 2.11.4 locally, 0 issues after the fix; CI uses v2.15.0, not yet run), go test -count=1 ./... (all pass). One earlier TestTLS run failed with address already in use on port 1111 and passed on rerun; nothing else held the port afterward.
Not run: the GitHub Actions workflow, and a v2.15.0 lint run. Review was my own read of a four-file diff; no sub-agent lenses.

v3.5.1 is to be tagged after merge.

Fixes ENG-584

@thrawn01
thrawn01 merged commit aad4c73 into main Oct 29, 2026
1 check passed
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