Repository navigation
chore: Build on the Go 1.27 toolchain - #353
Merged
Merged
Conversation
Go 1.26 stops getting security fixes when Go 1.28 ships in February 2027. Building on 1.27 now keeps the binaries patched and the fleet on one Go line. Key features/changes: - Move the Nix flake and dev container to Go 1.27 - Move the go.mod toolchain line to go1.27.3, which actions/setup-go uses over the go line, so CI also builds and tests on 1.27 - Leave the go line unchanged, so the binaries keep their current GODEBUG runtime defaults; raising it is a separate change
ecv
marked this pull request as ready for review
November 3, 2026 18:44
ecv
enabled auto-merge
November 3, 2026 18:45
andrewb3000
approved these changes
Nov 3, 2026
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
Go 1.26 stops getting security fixes in February 2027. This builds and tests datumctl on Go 1.27, with runtime behaviour unchanged (the go.mod
goline stays at 1.26.0).go_1_26togo_1_272-1.27-trixietoolchainmoves togo1.27.3, whichactions/setup-gouses over thegoline, so the shared CI workflow builds and tests on 1.27This is step 1 of https://github.com/datum-cloud/infra/issues/8340 per the guide.
The repo pins no golangci-lint or controller-gen, so neither moved.
Test plan
Related to #349