Skip to content

chore: bump golangci-lint to v2.5.0#4571

Open
ogulcanaydogan wants to merge 2 commits into
open-policy-agent:masterfrom
ogulcanaydogan:chore/bump-golangci-lint-v2.5
Open

chore: bump golangci-lint to v2.5.0#4571
ogulcanaydogan wants to merge 2 commits into
open-policy-agent:masterfrom
ogulcanaydogan:chore/bump-golangci-lint-v2.5

Conversation

@ogulcanaydogan
Copy link
Copy Markdown
Contributor

What this PR does / why we need it

Bump golangci-lint from v2.4.0 (released 2025-08-14) to v2.5.0 (released 2025-09-21). This is a single-minor-version step intended to keep the linter close to upstream without skipping ahead too far in one go.

The v2.5.0 release is mostly dependency bumps for underlying linters (e.g. revive 1.11.0 to 1.12.0, gosec 2.22.7 to 2.22.8, testifylint 1.6.1 to 1.6.4) plus one new linter (unqueryvet). The gatekeeper .golangci.yaml uses default: none with an explicit enable list, so unqueryvet is not activated automatically.

Which issue(s) this PR fixes

Part of keeping tooling current; no specific issue.

Special notes for your reviewer

If CI lint passes here, a follow-up PR can step to v2.6.x or v2.7.x. Skipping straight to v2.12.x would lump several minor releases together and make any new lint failures harder to diagnose.

Full v2.5.0 changelog: https://golangci-lint.run/docs/product/changelog/#250

Bump golangci-lint from v2.4.0 to v2.5.0 (released 2025-09-21). The
release is mostly dependency bumps for underlying linters (revive
1.11.0 to 1.12.0, gosec 2.22.7 to 2.22.8, testifylint 1.6.1 to 1.6.4,
etc.) plus one new opt-in linter (unqueryvet). Since the gatekeeper
.golangci.yaml uses `default: none` with an explicit enable list, the
new linter is not activated automatically.

Signed-off-by: Ogulcan Aydogan <[email protected]>
Copilot AI review requested due to automatic review settings May 17, 2026 08:57
@ogulcanaydogan ogulcanaydogan requested a review from a team as a code owner May 17, 2026 08:57
@codecov-commenter
Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 44.43%. Comparing base (3350319) to head (923e1a7).
⚠️ Report is 700 commits behind head on master.

❗ There is a different number of reports uploaded between BASE (3350319) and HEAD (923e1a7). Click for more details.

HEAD has 1 upload less than BASE
Flag BASE (3350319) HEAD (923e1a7)
unittests 2 1
Additional details and impacted files
@@             Coverage Diff             @@
##           master    #4571       +/-   ##
===========================================
- Coverage   54.49%   44.43%   -10.07%     
===========================================
  Files         134      282      +148     
  Lines       12329    20717     +8388     
===========================================
+ Hits         6719     9206     +2487     
- Misses       5116    10714     +5598     
- Partials      494      797      +303     
Flag Coverage Δ
unittests 44.43% <ø> (-10.07%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

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.

3 participants