🔴 go.mod requires Go 1.25.0 but Dockerfile still uses golang:1.24.12, breaking Docker builds

The go directive in go.mod was bumped from 1.24.0 to 1.25.0. Since Go 1.21+, the go directive is enforced as a hard minimum version requirement. However, the Docker build for the Go feature server at go/infra/docker/feature-server/Dockerfile:1 uses FROM golang:1.24.12. When the Dockerfile runs go build -o feast ./go/main.go (go/infra/docker/feature-server/Dockerfile:24), it will fail because Go 1.24.12 cannot build a module requiring Go 1.25.0. The build will error with something like go: go.mod requires go >= 1.25.0 (running go 1.24.12).

The go.mod now requires go 1.25.0, but the Dockerfile at go/infra/docker/feature-server/Dockerfile still uses FROM golang:1.24.12 as its base image. This will cause Docker builds to fail because the Go toolchain in the container (1.24.12) is older than what go.mod requires (1.25.0). The fix is to update the FROM line in go/infra/docker/feature-server/Dockerfile to use a golang:1.25.x image (e.g. golang:1.25.0 or later). Search for any other Dockerfiles or CI configurations that specify a Go version and may need updating as well.

Was this helpful? React with 👍 or 👎 to provide feedback.