Repository navigation
Conversation
Move the Go runtime from 1.26 to 1.27 at every coupled location: - go directive 1.26.0 -> 1.27.0; go mod tidy under the 1.27 directive merges the second direct require block into the first and moves three // indirect entries into the indirect block (no version change, go.sum unchanged) - install-go.sh and the lake-builder image: Go 1.26.9 -> 1.27.2 with new SHA256 checksums for linux/amd64 and linux/arm64 - golang:1.26-bookworm -> golang:1.27-bookworm in both backend Dockerfiles - devcontainer base image 1-1.26-bookworm -> 2-1.27-bookworm; the 1-* tag line is no longer published, so the old reference no longer resolves - workflow step labels follow the new version Signed-off-by: DoDiODev <DoDiDev@proton.me>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Moves the backend from Go 1.26 to Go 1.27 (1.27.2) at every place that pins the Go version. Go 1.28 is expected around February 2027, after which 1.26 no longer receives security fixes.
This builds on #9210 (golangci-lint v2.14.0): the released golangci-lint v2.12.2 binary is built with Go 1.26 and refuses to run on a module that targets Go 1.27.
Changes
backend/go.modgo 1.26.0→go 1.27.0, plus thego mod tidyreordering described belowbackend/scripts/install-go.sh1.26.9→1.27.2, new SHA256 for linux-amd64 / linux-arm64 (from go.dev)devops/docker/lake-builder/DockerfileGO_VERSION/GO_SHA256→ 1.27.2backend/Dockerfile,backend/Dockerfile.localgolang:1.26-bookworm→golang:1.27-bookworm.devcontainer/Dockerfiledevcontainers/go:1-1.26-bookworm→devcontainers/go:2-1.27-bookwormtest.yml,test-e2e.yml(2×),golangci-lint.yml,migration-script-lint.ymlgo.modreordering: with thego 1.27.0directive,go mod tidymerges the second block of direct requirements into the first and moves three// indirectentries into the indirect block. No module version changes andgo.sumis untouched. Without it, thego mod tidycheck in CI would fail. With the oldgo 1.26.0directive, Go 1.27.2 leavesgo.modas it is, so the reordering comes from the directive alone.Dev container: the
1-*tag line ofmcr.microsoft.com/devcontainers/gois no longer published, so the current1-1.26-bookwormreference no longer resolves. This PR switches to the maintained2-*line.Verification
go mod tidyleavesgo.mod/go.sumunchangedmake mock,make build(includingswag),make unit-testwith Go 1.27.2go vet ./...CI installs Go through
install-go.shand therefore tests 1.27.2 directly. The lake-builder change takes effect once a new builder image is published (#9209).