[vdemeester]: Alright, this was discussed during today's working group (23rd September 2026), and the decision was to even be proactive around update go version on supported release branches. Essentially, golang supports 2 versions at time (at the time of writing, 1.26 and 1.27), so we should make sure to use either one of them on the release branch (and main of course) we support. I think I'll close this issue and create a new one to discuss how we can do this (aka what level of automation, etc..)

Context: GitHub issue tektoncd/pipeline#10762 (closed, 1 comments, reported 2026-09-16): ## What happened `sigstore/sigstore` `v1.10.10` (released after `v1.10.9`) bumped its own `go.mod` from `go 1.25.0` to `go 1.27.0` (sigstore/sigstore#2415). Because Go's module graph rules take the max `go` directive across all dependencies, updating to `v1.10.10` forces the consuming `go.mod`'s `go` line up to `1.27.0` too , as a side effect of what dependabot presents as an unremarkable "patch" bump (`kind/misc`, `semver-patch`). This has now happened on two release branches: - **`release-v1.15.x`**: already merged via `[release-v1.15.x] bump github.com/sigstore/sigstore/pkg/signature/k