chore(deps): update github-actions-non-major

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
docker/setup-buildx-action	action	minor	v4.2.0 → v4.3.0
docker/setup-buildx-action (changelog)	action	digest	bb05f3f → 37fe631
golangci/golangci-lint	uses-with	minor	v2.12.2 → v2.13.0

---

Release Notes

docker/setup-buildx-action (docker/setup-buildx-action)

v4.3.0

Compare Source

• Bump @​docker/actions-toolkit from 0.92.0 to 0.95.0 in #​595
• Bump brace-expansion from 1.1.13 to 1.1.18 in #​600
• Bump js-yaml from 5.2.0 to 5.3.0 in #​585
• Bump postcss from 8.5.10 to 8.5.25 in #​598
• Bump undici from 6.27.0 to 6.28.0 in #​601

Full Changelog: docker/setup-buildx-action@v4.2.0...v4.3.0

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

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: add option `exclude-
   • goconst: from 1.10.0 to 1.11.0 (new option: ignore-map-keys)
   • 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) types`
   • unparam: from 2dd26e2 to 2dd26e2
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: (in timezone America/New_York)

• Branch creation
  • At any time (no schedule defined)
• 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

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

---

This PR was generated by Mend Renovate. View the repository job log.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[github-actions]

✅ Supply Chain Verification Results

✅ PASSED

📦 SBOM Summary

• Components: 1753

🔍 Vulnerability Scan

Severity	Count
🔴 Critical	0
🟠 High	0
🟡 Medium	5
🟢 Low	2
Total	11

📎 Artifacts

• SBOM (CycloneDX JSON) and Grype results available in workflow artifacts

---

_{Generated by Supply Chain Verification workflow • View Details}

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.