Commit c17850f
committed
fix(ci): re-pin golangci-lint install.sh checksum for v2.13.1
setup-tools fetches install.sh from a version-scoped URL
(raw.githubusercontent.com/golangci/golangci-lint/${VERSION}/install.sh)
but verified it against a version-independent hardcoded constant. When
#2351 bumped linting.golangci_lint from v2.12.2 to v2.13.1, the pin went
stale and every E2E job started failing:
Expected: d32d3534... (install.sh at v2.12.2)
Actual: 1022ddb4... (install.sh at v2.13.0 and v2.13.1)
Only tests/E2E is affected because it is the sole job that runs
tools/setup-tools; tests/Lint uses golangci/golangci-lint-action, which
does its own checksum handling.
Re-pin to the v2.13.1 hash and document the coupling inline, since
Renovate bumps the version without knowing the hash exists.
Follow-up: GRYPE_INSTALL_SHA256 has the same shape but tracks the
upstream main branch, so it can break with no version bump at all. Both
would be better served by the release-checksums.txt pattern already used
for flux and zarf in this file.
Signed-off-by: Mark Chmarny <mark@chmarny.com>1 parent 735a311 commit c17850f
1 file changed
Lines changed: 4 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
378 | 378 | | |
379 | 379 | | |
380 | 380 | | |
381 | | - | |
| 381 | + | |
| 382 | + | |
| 383 | + | |
| 384 | + | |
382 | 385 | | |
383 | 386 | | |
384 | 387 | | |
| |||
0 commit comments