Skip to content

ci: bump golangci-lint from v2.9 to v2.11#2489

Open
dgageot wants to merge 1 commit intodocker:mainfrom
dgageot:board/update-golangci-lint-and-enable-new-lint-0544785e
Open

ci: bump golangci-lint from v2.9 to v2.11#2489
dgageot wants to merge 1 commit intodocker:mainfrom
dgageot:board/update-golangci-lint-and-enable-new-lint-0544785e

Conversation

@dgageot
Copy link
Copy Markdown
Member

@dgageot dgageot commented Apr 21, 2026

Bumps the golangci-lint version used in CI from v2.9 to v2.11 (latest stable is v2.11.4, released 2026-03-22).

New linters

None to activate. Per the official CHANGELOG, v2.10.x and v2.11.x only contain bug fixes and updates to existing linters (e.g. new gosec rules, revive rule renames, errcheck default exclusions, staticcheck 0.7). No new standalone linters were introduced.

All relevant linters from recent releases (modernize, godoclint, unqueryvet, iotamixing, embeddedstructfieldcheck, nilnesserr, exptostd, fatcontext, …) are already enabled in .golangci.yml.

Validation

Run locally against v2.11.3:

  • golangci-lint config verify → clean
  • golangci-lint run → 0 issues
  • All 63 configured linters resolve correctly

Note

v2.11.0 has a ⚠️ breaking change in revive (package-related checks moved from var-naming to a new package-naming rule). This only affects configs that explicitly configure var-naming, which ours does not — so no action required.

No new standalone linters were added between v2.9 and v2.11.x,

so no configuration changes are required in .golangci.yml.

Assisted-By: docker-agent
@dgageot dgageot requested a review from a team as a code owner April 21, 2026 15:40
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