Skip to content

build: upgrade Go toolchain to 1.27.3 - #2654

Merged
Roasbeef merged 2 commits into
btcsuite:masterfrom
Roasbeef:build/go-1.27.3
Oct 21, 2026
Merged

Roasbeef merged 2 commits into
btcsuite:masterfrom
Roasbeef:build/go-1.27.3

Conversation

@Roasbeef

@Roasbeef Roasbeef commented Oct 21, 2026 •

Copy link
Copy Markdown
Member

In this PR, we upgrade CI, Docker builds and release binaries to Go 1.27.3. The release adds the crypto/x509 mitigation for CVE-2026-111943, which rejects certificate chains containing affected intermediate CA keys. We also move every module's go directive to Go 1.26.10, the latest release on the previous supported branch, and update the documented minimum and release instructions.

The go directive expresses only a minimum version, so it cannot encode the patched floor on both supported branches. Use Go 1.26.10 or newer on the Go 1.26 branch, and Go 1.27.3 or newer on the Go 1.27 branch; Go 1.27.0 through 1.27.2 do not include this mitigation. The release script continues to require Go 1.27.3 for release builds.

Both Docker build images use the verified golang:1.27.3-alpine3.24 index digest, sha256:f2c872bcee949b7be9c490efd02b48a8a2fbf947cdf533f1c58525ec9d8170fd.

Validation:

  • make check-go-versions
  • make build
  • make unit
  • go test ./... in all nine nested modules
  • git diff --check

All checks ran with Go 1.27.3 on darwin/arm64.

In this commit, we upgrade CI, Docker builds and release binaries to Go 1.27.3. This release adds the crypto/x509 mitigation for CVE-2026-111943, which distrusts affected intermediate CA keys. We also move every module language version to Go 1.26.10, the latest release on the previous supported branch.
In this commit, we spell out the patched Go point-release floor for each supported branch. The go directive can require a minimum version, but it cannot prevent builds with Go 1.27.0 through 1.27.2.
@Roasbeef
Roasbeef merged commit a1cc50b into btcsuite:master Oct 21, 2026
6 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.

1 participant