zooqueen 23753a4cfe state the toolchain this binary is built with, and keep the caller on v1 ...

go.mod said `go 1.26`, a floor of 1.26.0, while the Dockerfile pins
golang:1.26.5-bookworm. Nothing imports this — it is a binary — so the directive
constrains only its own build, and naming the patch says which toolchain it is
actually built and tested with rather than one it happens to clear.

The caller goes back to @v1. Pinning an immutable tag there looked like a canary
and is not one: this forge leaves GITHUB_WORKFLOW_REF unset, so build.yml clones
its own bin/ tools from `v1` whatever ref the caller named. A caller pinned
elsewhere gets that build.yml against v1's tools, which is the skew the
pipeline's own tool check exists to catch.

2026-08-19 22:54:16 -07:00

..

cicd.yml

state the toolchain this binary is built with, and keep the caller on v1

2026-08-19 22:54:16 -07:00