Skip to content

build: bump Go to 1.26.11 - #994

Merged
glours merged 1 commit into
compose-spec:mainfrom
ndeloof:bump-go-1.26.11
Nov 12, 2026
Merged

glours merged 1 commit into
compose-spec:mainfrom
ndeloof:bump-go-1.26.11

Conversation

@ndeloof

@ndeloof ndeloof commented Nov 10, 2026 •

Copy link
Copy Markdown
Collaborator

What this PR does, in one sentence

The Go version of the module moves from 1.26.0 to 1.26.11, the release which carries the latest security fixes of the 1.26 line.

Context

go1.26.11 (and go1.27.4) was released today with security fixes to cgo, the go command, the compiler, the linker and the net/http package. The test matrix already follows the latest 1.26 and 1.27 releases, but the CI jobs which read their Go version from go.mod (lint, deepcopy, license check, vet, go mod tidy) and the release workflow still use go1.26.0.

What the PR brings

  • go.mod declares go 1.26.11, so those jobs run with the patched toolchain.
  • Applications importing compose-go need go1.26.11 at least to build with this version (the Go command fetches it by itself when GOTOOLCHAIN allows it).

Not changed: the Go versions of the test matrix (1.26 and 1.27, always the latest patch) and the Go image of ci/Dockerfile (golang:1.26).

🤖 Generated with Claude Code

@ndeloof
ndeloof requested a review from glours as a code owner November 10, 2026 21:36
@glours
glours enabled auto-merge (rebase) November 12, 2026 09:54
go1.26.11 and go1.27.4 include security fixes to cgo, the go command, the
compiler, the linker and the net/http package.

The CI jobs which read the Go version from go.mod (lint, deepcopy, license
check, vet, mod tidy) and the release workflow were still using go1.26.0.

release notes: https://go.dev/doc/devel/release#go1.26.11

Signed-off-by: Nicolas De Loof <nicolas.deloof@gmail.com>
@glours
glours merged commit 8d14221 into compose-spec:main Nov 12, 2026
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants