Fast-follow on PR #59. The merge to main triggered release.yml run 107 which failed at go mod download with:
go: go.mod requires go >= 1.25.0 (running go 1.23.12; GOTOOLCHAIN=local)
The M7/M8 batch bumped go.mod to go 1.25.0 but the Dockerfile's builder stage still pinned golang:1.23-bookworm. Bumping to golang:1.25-bookworm matches.
No CI paths trigger on Dockerfile changes (correctly — the Dockerfile only matters at image build time), so this PR will go in unverified at the lint/test level; the verification is the next release.yml run on main going green.
After merge I'll force-move v2026.06.01 to the new main HEAD so the image tag rebuilds cleanly.
Fast-follow on PR #59. The merge to main triggered `release.yml` run 107 which failed at `go mod download` with:
```
go: go.mod requires go >= 1.25.0 (running go 1.23.12; GOTOOLCHAIN=local)
```
The M7/M8 batch bumped `go.mod` to `go 1.25.0` but the Dockerfile's builder stage still pinned `golang:1.23-bookworm`. Bumping to `golang:1.25-bookworm` matches.
No CI paths trigger on Dockerfile changes (correctly — the Dockerfile only matters at image build time), so this PR will go in unverified at the lint/test level; the verification is the next `release.yml` run on main going green.
After merge I'll force-move `v2026.06.01` to the new main HEAD so the image tag rebuilds cleanly.
The release.yml build on main HEAD c0185357 failed with:
go: go.mod requires go >= 1.25.0 (running go 1.23.12; GOTOOLCHAIN=local)
go.mod was bumped to 1.25.0 during the M7/M8 batch but the
Dockerfile's builder stage still pinned golang:1.23-bookworm. Bump
to golang:1.25-bookworm to match.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Fast-follow on PR #59. The merge to main triggered
release.ymlrun 107 which failed atgo mod downloadwith:The M7/M8 batch bumped
go.modtogo 1.25.0but the Dockerfile's builder stage still pinnedgolang:1.23-bookworm. Bumping togolang:1.25-bookwormmatches.No CI paths trigger on Dockerfile changes (correctly — the Dockerfile only matters at image build time), so this PR will go in unverified at the lint/test level; the verification is the next
release.ymlrun on main going green.After merge I'll force-move
v2026.06.01to the new main HEAD so the image tag rebuilds cleanly.