Skip to content

ci: pin staticcheck to a release that supports go 1.25 - #242

Closed
barnabasbusa wants to merge 1 commit into
masterfrom
bbusa/pin-staticcheck
Closed

barnabasbusa wants to merge 1 commit into
masterfrom
bbusa/pin-staticcheck

Conversation

@barnabasbusa

Copy link
Copy Markdown
Contributor

The code checks install staticcheck@latest, and staticcheck v0.8.x now requires go 1.26 while CI runs go 1.25 with GOTOOLCHAIN=local, so every PR fails at the install step (honnef.co/go/[email protected] requires go >= 1.26.0). This pins v0.7.0, the last release supporting go 1.25; it reports no issues on master.

@barnabasbusa

Copy link
Copy Markdown
Contributor Author

Superseded by #243, which bumps Go to 1.26 instead of pinning staticcheck.

@barnabasbusa
barnabasbusa deleted the bbusa/pin-staticcheck branch October 13, 2026 11:14

@redpandabot redpandabot Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This pins the CI staticcheck install from @latest to @v0.7.0 in .github/workflows/_shared-check.yaml. v0.7.0's go.mod requires go 1.25.0 and all its transitive dependencies require no more than go 1.24.0, matching the workflow's go 1.25.x setup, whereas v0.8.0+ require go 1.26.0. OSV reports no vulnerabilities for v0.7.0, and the change is minimal and correct.


Reviewed 1 changed file(s) @ 230c98e0 — no blocking issues found.
"Adding manpower to a late software project makes it later." — Fred Brooks

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.

1 participant