From cb74b0f0f5d3290ffb0fcbb56a2e8f40eebe9989 Mon Sep 17 00:00:00 2001 From: tannevaled Date: Sun, 4 Oct 2026 21:13:43 +0200 Subject: [PATCH] go 1.27.1, which is what CI has been building with The go directive said 1.26.4 while every lane of this repository's CI pins go-version 1.27.1. The version declared and the version tested had not been the same for weeks. Measured on a sibling where the pin was still 1.26 (go-images/jpeg2000#28), govulncheck on the same code: toolchain in packages imported in modules required go1.26.4 1 10 go1.27.1 0 0 Nothing was CALLED in either case; what 1.26.4 carries is its own standard library -- GO-2026-4970 in os, and GO-2026-6218, 6091, 6090, 6089, 6088, 5972, 5942, 5026 and 5856 in stdlib, fixed across 1.26.5 and 1.26.6. govulncheck on this module is silent under 1.27.1: x/sys is already v0.48.0 here, past GO-2026-5024. 1.27.1 and not 1.27, because that is the style this file already used and the advisories are patch-level: "1.27" would admit a toolchain with none of 1.27.1's fixes. go vet, the whole suite and exact 100% coverage pass under 1.27.1, and 1.27's gofmt wants nothing this tree does not already have -- checked, because a note of mine records 1.27 reindenting where the local gofmt cannot see it. --- go.mod | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/go.mod b/go.mod index d522541..5b41d9c 100644 --- a/go.mod +++ b/go.mod @@ -1,6 +1,6 @@ module github.com/go-pdfkit/conformance -go 1.26.4 +go 1.27.1 require ( github.com/go-gfx/gfx v0.34.0