lukaszraczylo 53afd9890f ci: pin govulncheck to v1.7.0 ...

govulncheck@latest resolves to v1.8.0, which declares go 1.26.0 in its
module file. Every job in this workflow pins go-version 1.25.x, so the
install step fails before any scanning runs, which fails ci-success and
skips the release job.

v1.7.0 declares go 1.25.0 and installs on the pinned toolchain. This also
matches the convention used for staticcheck, which is already pinned to
an exact version. Pinning the binary does not freeze the vulnerability
database, which govulncheck fetches at run time.

Claude-Session: https://claude.ai/code/session_01Fu2wXqGUrfVBi5aLafKk8U

2026-09-15 11:34:33 +01:00

..

workflows

ci: pin govulncheck to v1.7.0

2026-09-15 11:34:33 +01:00

FUNDING.yml

Add sponsorship

2026-05-09 13:56:40 +01:00