Skip to content

fix: build with Go 1.27.3 (GO-2026-6809 in crypto/x509) - #128

Merged
ovander merged 1 commit into
mainfrom
fix/go-1.27.3
Nov 4, 2026
Merged

ovander merged 1 commit into
mainfrom
fix/go-1.27.3

Conversation

@ovander

@ovander ovander commented Nov 4, 2026

Copy link
Copy Markdown
Owner

What it changes

govulncheck now fails on every run, main included, with GO-2026-6809: Go 1.27.2's crypto/x509 trusts compromised intermediate certificates. Go 1.27.3 fixes it. The reported trace is socrate.Client.StreamSecurityEvents → x509.Certificate.Verify, but any TLS call reaches it. The failure first showed on #127, which only touches workflow YAML.

This PR moves the toolchain to 1.27.3:

  • the toolchain line in go.mod;
  • the go-version of the CI jobs that run the toolchain (build & test, golangci-lint, govulncheck);
  • the versions quoted in README, CONTRIBUTING and CLAUDE.md.

The go line, the floor importers need, stays at 1.26.0. Importers get the fix by building with Go 1.27.3 or later. tenure-api already does.

A line is added under ## [Unreleased] (Security) in CHANGELOG.md.

How it was tested

Locally with Go 1.27.3:

  • go mod tidy (go.sum unchanged);
  • go build ./...;
  • go vet ./...;
  • go test -race ./...;
  • golangci-lint run ./... (0 issues).

govulncheck cannot reach vuln.go.dev from my environment, so this PR's own CI run is the check that matters.

Exported API

None.


Generated by Claude Code

govulncheck now fails every run: Go 1.27.2's crypto/x509 trusts
compromised intermediate certificates (GO-2026-6809), reached from any
TLS call such as socrate.Client.StreamSecurityEvents; Go 1.27.3 fixes
it. The toolchain line, the CI jobs and the docs move to 1.27.3. The go
line, the floor importers need, stays at 1.26.0.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013GcASrGGa8qWVV78mbXJoa
@ovander
ovander merged commit 9bdb831 into main Nov 4, 2026
4 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.

2 participants