Skip to content

ci: pin golangci-lint version for reproducibility#1

Open
DojoGenesis wants to merge 2 commits intomainfrom
ci/pin-golangci-lint
Open

ci: pin golangci-lint version for reproducibility#1
DojoGenesis wants to merge 2 commits intomainfrom
ci/pin-golangci-lint

Conversation

@DojoGenesis
Copy link
Copy Markdown
Owner

Summary

  • Pins golangci-lint binary from version: latest to version: v2.1.6 in .github/workflows/ci.yml
  • version: latest resolves to whatever GitHub's runner happens to cache — when that bumps, green CI turns red with no code change
  • Local golangci-lint 2.11.4 already surfaces 9 SA5011 findings the pinned-latest CI doesn't see; this closes that drift window

Drift incident reference

This sweep was triggered by the plugins+gateway remediation run (DojoGenesis/gateway commits 07cb863, ac29ba8, 981e081) where SA5011 nil-pointer dereference findings appeared locally but not in CI — exactly the failure mode that unpinned latest allows.

Test plan

  • Verify CI lint step picks up v2.1.6 binary on next push
  • Confirm no new lint errors introduced (baseline is clean post-SA5011 fixes)

🤖 Generated with Claude Code

TresPies-source and others added 2 commits April 22, 2026 19:05
Pins golangci-lint binary to v2.1.6 instead of `version: latest` to
prevent silent CI breakage when GitHub's runner-cached "latest" bumps.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@DojoGenesis
Copy link
Copy Markdown
Owner Author

Bumped golangci-lint-action v2.1.6 → v2.11.4 to fix Go 1.25.6 build failure (prior version built against Go 1.24 only).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants