Skip to content

Require Go 1.26.10 to build - #196

Merged
thrawn01 merged 1 commit into
mainfrom
thrawn01/eng-581-require-go-12610-to-build
Oct 29, 2026
Merged

thrawn01 merged 1 commit into
mainfrom
thrawn01/eng-581-require-go-12610-to-build

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). dispatch calls https://api.linear.app/graphql, and go.mod allowed any Go from 1.26.2, so a dispatch binary could be built with the hole. After this change go.mod requires 1.26.10 and CI, which reads go-version-file: go.mod, tests on it. Mirrors ENG-578 for gubernator.

After merge, an already installed dispatch keeps the old Go until make install is run again.

Implementation

  • go.mod: go 1.26.2 becomes go 1.26.10. No workflow edit is needed because both workflows take the version from go.mod.
  • The eval fixtures' go.mod files (go 1.22) are untouched.

Verified locally on Go 1.26.10 (the toolchain switched itself after the edit): go vet ./... and make test pass, and a go install ./cmd/dispatch binary reports go1.26.10 in go version -m. I ran no sub-agent reviews for this one-line change, and make ci and the CI run on GitHub are not yet seen.

Fixes ENG-581

Go releases before 1.26.10 accept certificate chains signed through eight compromised eMudhra intermediate CAs (GO-2026-6809), and dispatch calls Linear's API over HTTPS.
@thrawn01
thrawn01 merged commit b103d17 into main Oct 29, 2026
2 checks 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