chore(go): raise the go.mod language version to 1.27 - #178
Merged
Conversation
radutopala
force-pushed
the
chore/go-directive-1.27
branch
2 times, most recently
from
August 27, 2026 10:33
726b214 to
ff0dc5c
Compare
CodeQL's Go extractor caps at the language version in go.mod and forces GOTOOLCHAIN=local, so the directive was held at 1.26 while a separate toolchain line carried 1.27. codeql-action v4.37.9 now ships CodeQL CLI 2.26.4, so that split is retired: the go directive returns to 1.27.0 and the redundant toolchain line goes with it. docs/ moves the same way. The local codeql targets bump their bundle and Go container together, since raising one without the other hands the extractor export data it cannot read.
radutopala
force-pushed
the
chore/go-directive-1.27
branch
from
August 27, 2026 10:51
ff0dc5c to
2a15871
Compare
radutopala
enabled auto-merge (rebase)
August 27, 2026 10:52
Repository owner
deleted a comment from
radutopalama
Aug 27, 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
1 participant
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.
What
Retires the
go 1.26.0/toolchain go1.27.0split ingo.modand returns the language version to1.27.0.docs/go.modfollows. The localcodeqlmake targets move their bundle tov2.26.4and their Go container to1.27together.Why
The directive was pinned to 1.26 because CodeQL's Go extractor caps at the language version in
go.modand forcesGOTOOLCHAIN=local; seeinggo 1.27.0it pinned the runner to Go 1.26 and then could not load the module at all.codeql-actionv4.37.9 (2026-08-26) ships CodeQL CLI 2.26.4, so the gate that forced the split has moved.The bundle and Go container in the local targets have to move as a pair — raising one alone gives the extractor export data it cannot read, which is the same failure in a different place.
Verification
go build ./...,go vet ./...— clean on Go 1.27.0make lint-go— 608 issues before processing, 0 aftergo mod tidy -diff— no driftOne caveat worth stating plainly: this repo uses CodeQL default setup, so the CLI version is not pinned from here, and the most recent analyses before this PR were still reporting 2.26.3 rather than 2.26.4. Default-setup rollout lags the Action release. I also could not find a "Go 1.27 is now supported" entry in the Go extractor changelog, where every prior Go version bump has one.
So the CodeQL check on this PR is the real test. If it passes, the concern was unfounded. If it fails with
go.mod requires go >= 1.27.0 (running go 1.26.x; GOTOOLCHAIN=local), the gate has not actually moved for default-setup repos and this should wait.