Skip to content

chore: Take the Go 1.27 runtime defaults - #43

Merged
ecv merged 1 commit into
mainfrom
chore/go-1.27-runtime
Nov 3, 2026
Merged

ecv merged 1 commit into
mainfrom
chore/go-1.27-runtime

Conversation

@ecv

@ecv ecv commented Nov 3, 2026

Copy link
Copy Markdown
Contributor

Summary

Raises the go.mod go line from 1.26 to 1.27 so the binaries take Go 1.27's runtime defaults. Step 2 of https://github.com/datum-cloud/infra/issues/8340. Step 1 already moved the toolchain to go1.27.3.

Setting Old New Effect on this service
tracebacklabels 0 1 Crash tracebacks and debug=2 pprof goroutine dumps include pprof goroutine labels. The repo sets no pprof labels, so nothing changes.
x509sslcertoverrideplatform 0 1 crypto/x509 honours SSL_CERT_FILE / SSL_CERT_DIR on Windows and macOS only. No effect on Linux. The repo ships a Linux container image only (no goreleaser).

godebug lines kept

None.

Modules left alone

None. The repo has a single go.mod.

Test plan

  • Unit, e2e and lint pass
  • The service soaks in staging for a day with no new errors
  • Released to production on its own tag

Related to datum-cloud/infra#8340

Raise the go.mod go line to 1.27, so the binaries pick up Go 1.27's
default GODEBUG settings instead of 1.26's. Step 1 already builds on the
1.27 toolchain.

Key features/changes:
- tracebacklabels 0 -> 1: crash tracebacks and debug=2 pprof goroutine
  dumps include pprof goroutine labels. The service sets no labels, so
  nothing changes in practice.
- x509sslcertoverrideplatform 0 -> 1: crypto/x509 honours SSL_CERT_FILE
  and SSL_CERT_DIR on Windows and macOS. No effect on Linux, where the
  service runs.
@ecv
ecv marked this pull request as ready for review November 3, 2026 18:43
@ecv
ecv requested a review from andrewb3000 November 3, 2026 18:43
@ecv
ecv requested a review from a team as a code owner November 3, 2026 18:43
@ecv
ecv enabled auto-merge November 3, 2026 18:43
@ecv
ecv merged commit 009ef68 into main Nov 3, 2026
5 checks passed
@ecv
ecv deleted the chore/go-1.27-runtime branch November 3, 2026 18:44
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