From dcafce90e45928f9c4a217fe2f90c6c6fcc36d92 Mon Sep 17 00:00:00 2001 From: Wynne Pirini Date: Thu, 12 Nov 2026 10:29:04 +1300 Subject: [PATCH] chore(go): pin toolchain go1.26.11 for GO-2026-6859 main has been red since the guard was added: the `Deterministic claims guard` runs govulncheck, which reports Vulnerability #1: GO-2026-6859 Found in: net/http@go1.26.10 Fixed in: net/http@go1.26.11 go.mod pinned `toolchain go1.26.10`, so the scanner saw the vulnerable stdlib and the "clean security scan" claim failed. Nothing in the tree changed to cause it; the advisory simply landed under our pinned version. Bump the toolchain to the fixed release. The Docker builder already uses golang:1.27.3, so only the module's toolchain was behind. This is deliberately independent of any feature branch: it blocks every PR, and a security bump does not belong buried in an unrelated refactor. --- go.mod | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/go.mod b/go.mod index 0bfe70ec..b91c1df9 100644 --- a/go.mod +++ b/go.mod @@ -2,7 +2,7 @@ module github.com/calnode/calnode go 1.26.0 -toolchain go1.26.10 +toolchain go1.26.11 require ( github.com/disintegration/imaging v1.6.2