ci: bump the Go toolchain pin to 1.26.8 in go.mod and both workflow image digests (#473) #474
No reviewers
Labels
No labels
breaking
bug
documentation
enhancement
epic
good first issue
help wanted
refactoring
resolution/duplicate
resolution/invalid
resolution/wontfix
security
severity/critical
severity/high
severity/low
severity/medium
status/abandoned
status/blocked
status/needs-decision
status/needs-info
status/needs-verification
testing
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
sixfold-space/madtea!474
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "issue-473-ci-bump-the-go-toolchain-pin-to-1268-gomod-the-two"
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
Closes #473. The three places move together, per docs/contributing/ci.md ("Bumping the Go patch release"):
go.mod:go 1.26.6togo 1.26.8..forgejo/workflows/ci.yml(two jobs) and.forgejo/workflows/drift.yml(two jobs):docker.io/golang:1.26-trixiedigestb75d466d...to771f3162.....forgejo/workflows/drift.yml(one job):docker.io/golang:1.26digest0d1d3a79...to9d2f36f0....Digest provenance: Docker Hub reports the same index digest for
1.26-trixieand1.26.8-trixie(771f3162...), and for1.26and1.26.8(9d2f36f0...), both published 2026-09-02. So each pinned image bundles Go 1.26.8, which is whatscripts/check-go-version.shasserts against go.mod underGOTOOLCHAIN: local.Why now: the local gate failed its first step (go-version) on a 1.26.8 host against a 1.26.6 go.mod while finishing #440. The host is not downgraded.
Gate:
./scripts/gate.shfull run passes: go-version, selfheal, build, gofmt, vet, gofix, modtidy, third-party-licenses, hook-tests, adr-check, test-race, staticcheck, govulncheck, gosec, modernize, docs-verify, cross-compile, mcp-conformance.go mod tidy -diffis empty.Closes #473