From cb067a32dfdf7453282bd449955c0ecb1bcdbdab Mon Sep 17 00:00:00 2001 From: Konrad Heimel Date: Fri, 16 Oct 2026 00:37:44 +0200 Subject: [PATCH] :construction_worker: ci(verify): bump golangci-lint to v2.14.0 for Go 1.27.2 `go-version: stable` rolled to go1.27.2, which raised the stdlib export-data version to 5. golangci-lint v2.13.1 cannot decode it, so `verify` and `release-exitgate` have been red on main since 2026-10-06 and on every PR, with `(typecheck) could not import ... export data version 5 is greater than maximum supported version 4`. Reproduced locally with the go1.27.2 toolchain on PATH and GOTOOLCHAIN=local: v2.13.1 fails on internal/glob; v2.14.0 reports 0 issues on the whole tree and `config verify` passes. Both release binaries say "built with go1.27.0", so D-158's built-with heuristic does not catch a patch-level export-data bump; the env comment now says so. --- .github/workflows/verify.yaml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/.github/workflows/verify.yaml b/.github/workflows/verify.yaml index 056e807..d053e95 100644 --- a/.github/workflows/verify.yaml +++ b/.github/workflows/verify.yaml @@ -31,9 +31,12 @@ permissions: # minimum Go version must always be latest-1", so a release whose go.mod says # `go 1.N` supports Go 1.N+1. Failure signature: `(typecheck) could not import` # on paths rooted in /opt/hostedtoolcache/go/1.N.0/. Fix = bump this line. +# A Go PATCH release can trip it too: go1.27.2 raised the export-data version to 5, +# which v2.13.1 cannot decode although it was built with go1.27.0; v2.14.0 (also +# built with go1.27.0) reads it. Reproduce with the failing patch release on PATH. env: TASK_VERSION: v3.52.0 - GOLANGCI_LINT_VERSION: v2.13.1 + GOLANGCI_LINT_VERSION: v2.14.0 jobs: verify: runs-on: ubuntu-latest