mirror of
https://github.com/hanzokv/go.git
synced 2026-09-24 00:31:51 +00:00
zeekay
ba01baa778
First real runs on this fleet turned up three things the workflows had been getting for free from GitHub's hosted image. golangci-lint had no setup-go step. The linter shells out to `go` to load packages, and the job image does not carry a toolchain on PATH, so it exited on "go command required, not found" without reading a file. It sets up Go from go.mod now, like every other job here. doctests ran setup-go before checkout, so go.mod was not on disk when the action looked for it and the module cache degraded to a permanent miss. Checkout goes first. The e2e proxy builder was pinned to golang:1.24-alpine while go.mod requires 1.26.4. The official golang images set GOTOOLCHAIN=local, which makes the image the authority and refuses a newer directive, so `go mod download` stopped the compose build and took both docker.start and docker.e2e.start with it. The base moves up to 1.26-alpine; the version stays declared in exactly one place, go.mod, with the image as its floor. govulncheck is reporting three standard-library advisories against this module. That is a real finding and it stays visible.