Rebuild the Image with Go 1.27 (3.2.0-r2) #46

Closed
opened 2026-10-10 11:33:18 +00:00 by piscis · 0 comments
Owner

Parent

#45

What to build

The Image is built with a supported Go toolchain and published as Rebuild 2 of Upstream Version v3.2.0. Consumers on :3 get the Go 1.27 Image with a normal pull, and 3.2.0-r1 stays exactly what it was.

  • The build stage moves from Go 1.25 to the 1.27-alpine Go image, pinned by its current index digest. Look the digest up again when implementing and confirm GOLANG_VERSION is 1.27.x. If the build or the smoke test fails under 1.27, fall back to 1.26-alpine and say so in the pull request.

  • The Pin becomes Rebuild 2 of v3.2.0: the Rebuild's reference Upstream Version moves from v3.1.0 to v3.2.0, and the Rebuild number becomes 2. The Upstream Version and commit don't change.

  • Glossary: add Release ("the record on Forgejo of one published Image, named by its Image tag, with the changes since the previous Release that matter to Consumers"; avoid: changelog, version, tag). Extend Rebuild to say each Rebuild gets exactly one Release.

  • New ADR 0005, "A Release mirrors each published Image". It records:

    • a Release equals an Image tag;
    • the previous Release is found by ancestry;
    • CI creates Releases through the API after publishing, with no git push and no changelog file;
    • git-cliff was chosen over release-it;
    • the internal-scope filter;
    • the header built from the Pin.

    The ADR builds on ADR 0003 and doesn't replace it. It cites #45.

  • Commit and pull request title: fix: build the Image with Go 1.27, as Go 1.25 is out of support. The pull request says why: the standard library ships inside the static binary, and Go 1.25 no longer gets security fixes.

Acceptance criteria

  • make print-tag prints 3.2.0-r2
  • The Image's build stage runs Go 1.27.x (or 1.26.x, with the fallback explained in the pull request)
  • make lint and make verify-pin pass locally
  • CI on the pull request is green: multi-arch build, plus the smoke test of both architectures
  • The glossary defines Release, and Rebuild mentions its one Release
  • ADR 0005 exists and cites #45
  • The pull request is left for the maintainer to merge

Blocked by

None (can start immediately).

## Parent #45 ## What to build The Image is built with a supported Go toolchain and published as Rebuild 2 of Upstream Version v3.2.0. Consumers on `:3` get the Go 1.27 Image with a normal pull, and `3.2.0-r1` stays exactly what it was. - The build stage moves from Go 1.25 to the `1.27-alpine` Go image, pinned by its current index digest. Look the digest up again when implementing and confirm `GOLANG_VERSION` is 1.27.x. If the build or the smoke test fails under 1.27, fall back to `1.26-alpine` and say so in the pull request. - The Pin becomes Rebuild 2 of v3.2.0: the Rebuild's reference Upstream Version moves from v3.1.0 to v3.2.0, and the Rebuild number becomes 2. The Upstream Version and commit don't change. - Glossary: add **Release** ("the record on Forgejo of one published Image, named by its Image tag, with the changes since the previous Release that matter to Consumers"; avoid: changelog, version, tag). Extend **Rebuild** to say each Rebuild gets exactly one Release. - New ADR 0005, "A Release mirrors each published Image". It records: - a Release equals an Image tag; - the previous Release is found by ancestry; - CI creates Releases through the API after publishing, with no git push and no changelog file; - git-cliff was chosen over release-it; - the internal-scope filter; - the header built from the Pin. The ADR builds on ADR 0003 and doesn't replace it. It cites #45. - Commit and pull request title: `fix: build the Image with Go 1.27, as Go 1.25 is out of support`. The pull request says why: the standard library ships inside the static binary, and Go 1.25 no longer gets security fixes. ## Acceptance criteria - [ ] `make print-tag` prints `3.2.0-r2` - [ ] The Image's build stage runs Go 1.27.x (or 1.26.x, with the fallback explained in the pull request) - [ ] `make lint` and `make verify-pin` pass locally - [ ] CI on the pull request is green: multi-arch build, plus the smoke test of both architectures - [ ] The glossary defines **Release**, and **Rebuild** mentions its one Release - [ ] ADR 0005 exists and cites #45 - [ ] The pull request is left for the maintainer to merge ## Blocked by None (can start immediately).
Sign in to join this conversation.
No description provided.