release hardening: build with the Go that CI tests; digests are identity - #34
Merged
Merged
Conversation
Two repo-local pieces of the release-engineering track. **golang:1.26-alpine -> 1.25.5-alpine** in all three build Dockerfiles (release.toolchain.tested-is-shipped): go.mod says 1.25.5 and CI tests with it via go-version-file, but every image compiled with whatever 1.26.x the tag served that week. Evidence from CI covers the shipped binary only when they are the same toolchain; aligning DOWN to the tested version keeps this a hardening change instead of a toolchain upgrade. Moving to 1.26 stays available as its own deliberate bump that runs the full CI + e2e surface. Tag-level on purpose, not digest: base-image digest pins without a scan/refresh loop freeze CVE fixes, and stay deferred to the P0-7 scanner track. **A sha-<sha> tag is not "an exact, reproducible build"** (release.docs.match-artifacts): the quickstart README and compose comments promised reproducibility from a tag that names the source commit but remains a movable registry pointer. An operator who believes an artifact is pinned stops checking — the docs now direct exact pinning to the image digest (name@sha256:..., printed in each publish run's job summary), which is the only immutable reference. The moving v0.2 pin itself stays: that is a deliberate convenience-locator choice, now described as one.
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.
Summary
Two repo-local pieces of the release-engineering track (companion to
provin-line/auth#13).
golang:1.26-alpine→1.25.5-alpine(×3 Dockerfiles)release.toolchain.tested-is-shipped: go.mod says1.25.5and CI tests withit (
go-version-file), butcmd/network,cmd/pipelineanddeploy/quickstart/provisioncompiled with whatever 1.26.x the tag served thatweek — evidence from CI covers the shipped binary only when they are the same
toolchain. Aligning down to the tested version keeps this a hardening
change; moving to 1.26 stays available as its own deliberate bump that runs the
full CI + e2e surface.
Tag-level on purpose, not digest: base-image digest pins without a scan/refresh
loop freeze CVE fixes, and stay consciously deferred to the P0-7 scanner track.
A
sha-<sha>tag is not "an exact, reproducible build"release.docs.match-artifacts: the quickstart README and compose commentspromised reproducibility from a tag that names the source commit but remains a
movable registry pointer. An operator who believes an artifact is pinned stops
checking. The docs now direct exact pinning to the image digest
(
name@sha256:…, printed in each publish run's job summary — added inauth#13). The moving
v0.2pin itself stays: a deliberate convenience-locatorchoice, now described as one.
Test plan
The
composejob builds all three Dockerfiles from this commit with1.25.5-alpine and runs the 11 scenarios against the result — that green is the
tested-is-shipped verification, not a proxy for it.
golang:1.25.5-alpineexistence verified against Docker Hub (manifest HTTP 200) before pinning.
🤖 Generated with Claude Code