fix: build the Image with Go 1.27, as Go 1.25 is out of support #53

Merged
piscis merged 1 commit from piscis/go-1-27 into main 2026-10-10 13:19:32 +00:00
Owner

Summary

The Image is a static Go binary, so Go's standard library (TLS, HTTP, …) ships inside it. Its build stage ran Go 1.25, which is out of support and no longer gets security fixes. This moves the build stage to Go 1.27 and publishes the result as Rebuild 2 of Upstream Version v3.2.0, so Consumers on :3 get it with a normal pull while 3.2.0-r1 stays as it was.

 # Dockerfile
-FROM --platform=$BUILDPLATFORM golang:1.25-alpine@sha256:1ae0735f… AS build
+FROM --platform=$BUILDPLATFORM golang:1.27-alpine@sha256:f92b6ef8… AS build   # GOLANG_VERSION=1.27.2

 # pin.env (Upstream Version and commit unchanged)
 UPSTREAM_VERSION=v3.2.0
-REBUILD=1
-REBUILD_OF=v3.1.0
+REBUILD=2
+REBUILD_OF=v3.2.0

Also adds Release to the glossary (and notes each Rebuild gets exactly one Release), plus ADR 0005 "A Release mirrors each published Image", which records the release decisions from #45 on top of ADR 0003.

Evidence

  • Before: make print-tag → 3.2.0-r1; built binary: go1.25.x
    After: make print-tag → 3.2.0-r2; go version on the built binary → go1.27.2
  • make lint passes; make verify-pin → "Upstream tag v3.2.0 resolves to e30bb7e…, as the Pin expects."
  • Local make build + make smoke-test: amd64 and arm64 both PASS: 156 tools listed, version 3.2.0. No fallback to 1.26 was needed.

Merge Danger

Door: two-way

Merging publishes the new immutable tag 3.2.0-r2 and moves 3.2.0, 3.2, 3 and latest to it. A problem is fixed by a further Rebuild; 3.2.0-r1 stays pullable.

Blast Radius: Consumers

Everyone on a moving tag gets a binary built with a new toolchain on their next pull. Upstream v3.2.0 needs only Go 1.25.5, and the smoke test passes on both architectures.

Closes #46

## Summary The Image is a static Go binary, so Go's standard library (TLS, HTTP, …) ships inside it. Its build stage ran Go 1.25, which is out of support and no longer gets security fixes. This moves the build stage to Go 1.27 and publishes the result as Rebuild 2 of Upstream Version v3.2.0, so Consumers on `:3` get it with a normal pull while `3.2.0-r1` stays as it was. ```diff # Dockerfile -FROM --platform=$BUILDPLATFORM golang:1.25-alpine@sha256:1ae0735f… AS build +FROM --platform=$BUILDPLATFORM golang:1.27-alpine@sha256:f92b6ef8… AS build # GOLANG_VERSION=1.27.2 # pin.env (Upstream Version and commit unchanged) UPSTREAM_VERSION=v3.2.0 -REBUILD=1 -REBUILD_OF=v3.1.0 +REBUILD=2 +REBUILD_OF=v3.2.0 ``` Also adds **Release** to the glossary (and notes each Rebuild gets exactly one Release), plus ADR 0005 "A Release mirrors each published Image", which records the release decisions from #45 on top of ADR 0003. ## Evidence - **Before:** `make print-tag` → `3.2.0-r1`; built binary: `go1.25.x` **After:** `make print-tag` → `3.2.0-r2`; `go version` on the built binary → `go1.27.2` - `make lint` passes; `make verify-pin` → "Upstream tag v3.2.0 resolves to e30bb7e…, as the Pin expects." - Local `make build` + `make smoke-test`: amd64 and arm64 both `PASS: 156 tools listed`, version 3.2.0. No fallback to 1.26 was needed. ## Merge Danger **Door:** two-way Merging publishes the new immutable tag `3.2.0-r2` and moves `3.2.0`, `3.2`, `3` and `latest` to it. A problem is fixed by a further Rebuild; `3.2.0-r1` stays pullable. **Blast Radius:** Consumers Everyone on a moving tag gets a binary built with a new toolchain on their next pull. Upstream v3.2.0 needs only Go 1.25.5, and the smoke test passes on both architectures. Closes #46
fix: build the Image with Go 1.27, as Go 1.25 is out of support
All checks were successful
ci / build (pull_request) Successful in 1m26s
36ef19cdd4
piscis merged commit 6c4b18729e into main 2026-10-10 13:19:32 +00:00
piscis deleted branch piscis/go-1-27 2026-10-10 13:19:32 +00:00
Sign in to join this conversation.
No description provided.