Skip to content

chore: migrate golangci-lint to v2 to clear go 1.25 toolchain mismatch#43

Merged
ogulcanaydogan merged 1 commit into
mainfrom
chore/v0.2.30-golangci-lint-v2
May 20, 2026
Merged

chore: migrate golangci-lint to v2 to clear go 1.25 toolchain mismatch#43
ogulcanaydogan merged 1 commit into
mainfrom
chore/v0.2.30-golangci-lint-v2

Conversation

@ogulcanaydogan
Copy link
Copy Markdown
Owner

  • golangci-lint v1.64.8 was built with go1.24 and fails linting a go 1.25 target; every PR went red on Lint (Go) after the workflow toolchain bump in chore: pin workflows to go 1.25.x to clear govulncheck stdlib alerts #42. This PR unblocks the Lint job.
  • Bumps golangci-lint-action v6.5.2 to v7.0.1 (pinned SHA 9fae48ac) and binary v1.64.8 to v2.12.2; migrates .golangci.yml to v2 schema (top-level version: "2", settings under linters.settings, exclusions consolidated from issues.exclude-rules).
  • Five quickfix/style checks newly enabled by v2 defaults (QF1001, QF1011, QF1012, ST1005, ST1023) are explicitly disabled in linters.settings.staticcheck.checks to keep enforcement surface equivalent to v1; those 17 findings are queued for a follow-up refactor:/style: PR so this bump stays scope-clean.
  • No behavioural change to production code; go.mod and all package sources untouched.

golangci-lint v1.64.8 was built with go1.24 and cannot lint a go 1.25
target (raised by the toolchain bump in #42). Upgrade the action from
v6.5.2 to v7.0.1 and the binary from v1.64.8 to v2.12.2. Migrate
.golangci.yml to v2 schema (top-level version: "2", settings under
linters.settings, exclusions consolidated). Disable quickfix and style
checks QF1001/QF1011/QF1012/ST1005/ST1023 introduced by v2 defaults to
keep enforcement surface equivalent to v1; those refactors are queued
for a follow-up style: PR.
@ogulcanaydogan ogulcanaydogan merged commit 935824b into main May 20, 2026
17 checks passed
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