Skip to content

build: Go 1.27 - #7

Merged
AlexeyShalaev merged 2 commits into
masterfrom
build/go-1.27
Oct 7, 2026
Merged

AlexeyShalaev merged 2 commits into
masterfrom
build/go-1.27

Conversation

@AlexeyShalaev

Copy link
Copy Markdown
Member

Moves every build to Go 1.27 at once:

  • Dockerfile: the source stage on golang:1.27.1-alpine3.24 (the bump from build(deps): bump golang from 1.26.8-alpine3.24 to 1.27.1-alpine3.24 in the image group #2);
  • setup-go in CI, CodeQL and Publish: release binaries and govulncheck on 1.27;
  • the test matrix covers the two supported Go releases, 1.26 and 1.27 (1.25 gets no security fixes since 1.27);
  • go.mod: go 1.26.0, so go install needs Go 1.26 or newer; README, CONTRIBUTING and the docs say so;
  • the e2e harnesses and docs use golang:1.27 (git 2.47.3, as before).

Supersedes #2, which bumped only the source stage: the source image and the release would have been built with different compilers.

Release builds, the image's source stage, govulncheck and CodeQL move to
Go 1.27; the test matrix covers the two supported releases, 1.26 and
1.27, and go.mod requires 1.26, so go install needs Go 1.26 or newer.
Supersedes the Dockerfile-only bump in #2, which would have built the
source image and the release with different compilers.
Go 1.27 compresses the marker's data differently, and Go promises no
fixed gzip bytes across releases, so the golden bodies compare each
marker line with its data decoded. Pull request edits already compare the
body hash in the marker, not the compressed bytes.
@AlexeyShalaev
AlexeyShalaev merged commit 74076d4 into master Oct 7, 2026
38 of 40 checks passed
@AlexeyShalaev
AlexeyShalaev deleted the build/go-1.27 branch October 7, 2026 06:18
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.

1 participant