fix: build the Image with Go 1.27, as Go 1.25 is out of support #53
No reviewers
Labels
No labels
bug
enhancement
needs-info
needs-triage
ready-for-agent
ready-for-human
spec
wayfinder:grilling
wayfinder:map
wayfinder:prototype
wayfinder:research
wayfinder:task
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
vicoli-oss/docker-forgejo-mcp!53
Loading…
Reference in a new issue
No description provided.
Delete branch "piscis/go-1-27"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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
:3get it with a normal pull while3.2.0-r1stays as it was.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
make print-tag→3.2.0-r1; built binary:go1.25.xAfter:
make print-tag→3.2.0-r2;go versionon the built binary →go1.27.2make lintpasses;make verify-pin→ "Upstream tag v3.2.0 resolves to e30bb7e…, as the Pin expects."make build+make smoke-test: amd64 and arm64 bothPASS: 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-r2and moves3.2.0,3.2,3andlatestto it. A problem is fixed by a further Rebuild;3.2.0-r1stays 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