Skip to content

build: move the BFF's Go toolchain to 1.27.1 - #26

Merged
ovander merged 1 commit into
mainfrom
chore/go-1.27.1
Sep 27, 2026
Merged

ovander merged 1 commit into
mainfrom
chore/go-1.27.1

Conversation

@ovander

@ovander ovander commented Sep 27, 2026

Copy link
Copy Markdown
Owner

Step 3 of the toolchain review: Go 1.26.8 → 1.27.1.

  • bff/go.mod: toolchain go1.27.1.
  • bff/Dockerfile: golang:1.27.1-alpine.
  • SECURITY.md states the new pin.

CI reads bff/go.mod, and #24's drift check fails the build if CI and the Dockerfile disagree.

The go 1.25.0 line is unchanged, so GODEBUG defaults stay those of Go 1.25. Defaults that newer Go versions changed aren't adopted by this PR.

Verification (local, go1.27.1): go vet · golangci-lint v2.14.0 built with go1.27.1: 0 issues (the bff-lint job from #25) · go test -race ./... green. I couldn't verify locally that golang:1.27.1-alpine pulls.

Siblings: ovander/go-oauth2#249, ovander/backendkit#53, ovander/oauth2-monitoring#37.

🤖 Generated with Claude Code

https://claude.ai/code/session_01GKRxaeYxyDhmt42cehLsGA


Generated by Claude Code

Step 3 of the toolchain review. The pin moves from 1.26.8 to 1.27.1: the
toolchain line in go.mod, the golang image in the Dockerfile where there
is one, explicit CI versions, and the docs that state the pin. CI's drift
check keeps them equal.

The go line is unchanged at 1.25.x. That line, not the toolchain, sets
GODEBUG defaults, so the defaults Go 1.26 and 1.27 changed
(cryptocustomrand, tlssecpmlkem, urlstrictcolons, tracebacklabels,
x509sslcertoverrideplatform) keep their previous behaviour until the go
line is raised on purpose.

Verified on go1.27.1: build, vet, golangci-lint v2.14.0 built with
go1.27.1 (0 issues, caps off), and go test -race green.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GKRxaeYxyDhmt42cehLsGA
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