chore(deps): update dependency golangci/golangci-lint to v2.13.1

[scality-renovate]

This PR contains the following updates:

Package	Update	Change	Pending
golangci/golangci-lint	minor	v2.12.2 → v2.13.1	v2.13.2

---

Release Notes

golangci/golangci-lint (golangci/golangci-lint)

v2.13.1

Compare Source

Released on 2026-08-20

1. Linters bug fixes
   • ginkgolinter: from 0.23.1 to 0.24.0
   • gofmt: from d62b90e to e84e050
   • staticcheck: from 0.8.0-rc.1 to 0.8.0
   • wsl_v5: from 5.8.0 to 5.9.0

v2.13.0

Compare Source

Released on 2026-08-19

1. Enhancements
   • 🎉 go1.27 support
2. Bug fixes
   • fix: cache package facts
3. Linters new features or changes
   • dupword: from 0.1.7 to 0.1.8 (new option skip-raw-strings)
   • errcheck: from 1.10.0 to 1.20.0
   • exhaustruct_v5: from 4.0.0 to 5.0.2 (new configuration)
   • exhaustruct: deprecated and replaced by exhaustruct_v5
   • fatcontext: from 0.9.0 to 0.10.0 (new options: check-loops, check-function-literals)
   • goconst: from 1.10.0 to 1.11.0 (new options: ignore-map-keys, exclude-types)
   • gofumpt: from 0.9.2 to 0.11.0 (new options: extra.group-params, extra.clothe-returns, extra.balance-calls)
   • gomoddirectives: from 0.8.0 to 0.9.0 (new option: replace-allow-all)
   • gosec: from 2.26.1 to 2.27.1
   • govet-modernize: from 0.44.0 to 0.49.0 (fmtappendf is removed. New analyzers atomictypes, embedlit, errorsastype, importcomment, reflecttypeassert, slicesclip, and slicesbackward. waitgroup is renamed waitgroupgo)
   • iface: from 1.4.3 to 1.5.0 (new analyzer: unusedmethod)
   • noinlineerr: from 1.0.5 to 1.0.6
   • nonamedreturns: from 1.0.6 to 1.0.8 (new option: allow-unused-named-returns)
   • recvcheck: from 0.2.0 to 0.3.0 (new default exclusions)
   • unparam: from 5beb8c8 to 3f964bc
4. Linters bug fixes
   • clickhouse-go-linter: from 1.2.0 to 1.2.1
   • errname: from 1.1.1 to 1.1.2
   • exhaustruct: from 5.0.2 to 5.0.3
   • funcorder: add missing Function field
   • ginkgolinter: from 0.23.0 to 0.23.1
   • gocheckcompilerdirectives: from 1.3.0 to 1.4.0
   • gocritic: from 0.14.3 to 0.14.4
   • gomoddirectives: add missing IgnoreForbidden field
   • iface: from 1.4.2 to 1.4.3
   • mirror: from 1.3.0 to 1.3.3
   • nilnil: from 1.1.1 to 1.1.2
   • protogetter: from 0.3.20 to 0.3.21

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • "before 9am on monday"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate CLI.

[github-actions]

Dependency Bump Evaluation

Version change: golangci-lint v2.12.2 -> v2.13.1 (minor)
Files changed: .devcontainer/Dockerfile, Makefile (version pins only)

Changes (v2.13.0 + v2.13.1):

• go1.27 support, cache package facts fix
• Linter upgrades: errcheck 1.10->1.20, ginkgolinter->0.24.0, goconst->1.11.0, staticcheck 0.8.0-rc.1->0.8.0, unparam updated
• govet-modernize: new default-on analyzers (atomictypes, embedlit, errorsastype, importcomment, reflecttypeassert, slicesclip, slicesbackward), fmtappendf removed, waitgroup renamed to waitgroupgo
• Formatter updates: gofmt updated
• exhaustruct deprecated in favor of exhaustruct_v5 (not used by this project)

Breaking changes: None that affect this project directly. The exhaustruct deprecation is irrelevant (not enabled). The new default-on modernize analyzers could surface new findings -- the project enables modernize with only omitzero and newexpr disabled, so new analyzers will be active.

Security concerns: None -- golangci-lint is a dev-only tool with no runtime impact.

Impact on codebase:

• Project uses affected linters: errcheck, ginkgolinter, goconst, staticcheck, unparam, modernize, gofmt
• The errcheck major version jump (1.10->1.20) and new modernize analyzers are the main risk -- they could flag new patterns in existing code
• Any new findings will manifest as CI lint failures, providing a clear signal

CI status: build passed; lint, test, test-e2e, generate still in progress

Recommendation: SAFE TO MERGE (once CI is green)

Notes: This is a dev-only tooling bump with no runtime impact. The only risk is new lint findings from upgraded linters (especially new modernize analyzers and errcheck major bump), which CI will catch. If lint passes, merge with confidence.

— Claude Code