Update dependency golangci-lint to v1.57.1

[renovate]

This PR contains the following updates:

Package	Update	Change
golangci-lint	minor	1.56.2 -> 1.57.1

---

Release Notes

golangci/golangci-lint (golangci-lint)

v1.57.1

Compare Source

1. Fixes:
   • Ignore issues with invalid position (e.g. contextcheck).

v1.57.0

Compare Source

1. New linters
   • copyloopvar: https://github.com/karamaru-alpha/copyloopvar
   • intrange: https://github.com/ckaznocha/intrange
2. Updated linters
   • dupword: from 0.0.13 to 0.0.14
   • gci: from 0.12.1 to 0.12.3
   • ginkgolinter: from 0.15.2 to 0.16.1 (new option force-expect-to, validate-async-intervals, and forbid-spec-pollution)
   • go-critic: from 0.11.1 to 0.11.2
   • go-critic: support of enable-all and disable-all options
   • go-spancheck: from 0.5.2 to 0.5.3
   • gomodguard: from 1.3.0 to 1.3.1
   • govet: deprecation of check-shadowing ⚠️
   • govet: disable temporarily httpresponse because of a bug https://github.com/golang/go/issues/66259
   • misspell: add extra-words
   • musttag: from 0.8.0 to 0.9.0
   • nakedret: from 2.0.2 to 2.0.4
   • paralleltest: from 1.0.9 to 1.0.10
   • perfsprint: from 0.6.0 to 0.7.1 (new option strconcat)
   • protogetter: from 0.3.4 to 0.3.5
   • revive: add exclude option
   • sloglint: from 0.4.0 to 0.5.0 (new option no-global)
   • staticcheck: from 0.4.6 to 0.4.7
   • testifylint: from 1.1.2 to 1.2.0 (new option bool-compare)
   • unconvert: to HEAD (new options fast-math and safe)
   • wrapcheck: from 2.8.1 to 2.8.3
   • Disable copyloopvar and intrange on Go < 1.22
3. Enhancements
   • 🧩 New custom linters system https://golangci-lint.run/plugins/module-plugins/
   • 🎉 Allow running only a specific linter without modifying the file configuration (--enable-only)
   • Allow custom sort order for the reports (output.sort-order)
   • Automatically adjust the maximum concurrency to the container CPU quota if run.concurrency=0
   • Add verify command to check the configuration against the JSON Schema
   • Option to strictly follow Go generated file convention (issues.exclude-generated-strict)
   • Syntax to not override severity from linters (@linter)
   • Use severities from gosec
   • Create automatically directory related to output.formats.path
   • Use the first issue without inline on mergeLineIssues on multiple issues
4. Misc.
   • ⚠️ Inactivate deprecated linters (deadcode, exhaustivestruct, golint, ifshort, interfacer, maligned, nosnakecase, scopelint, structcheck, varcheck)
   • ⚠️ Deprecated CLI flags have been removed (deprecated since 2018)
   • ⚠️ Move show-stats option from run to output configuration section
   • ⚠️ Replace run.skip-xxx options by issues.exclude-xxx options
   • ⚠️ Replace output.format by output.formats with a new file configuration syntax
   • Internal rewrite of the CLI
   • Improve 'no go files to analyze' message
   • Use GOTOOLCHAIN=auto inside the Docker images
5. Documentation
   • ⚠️ Define the linter deprecation cycle https://golangci-lint.run/product/roadmap/#linter-deprecation-cycle
   • 🎉 Use information from the previous release to create linter pages
   • 🎉 Publish JSON schema on https://golangci-lint.run/jsonschema/golangci.jsonschema.json
   • Reorganize documentation pages
   • Add an explanation about the configuration file inside golangci-lint repository

⚠️ Important ⚠️

1. Deprecated linters are inactivated, you still need to disable them if you are using enable-all.
2. Deprecated CLI flags (about linter settings and deadline) have been removed.

---

Configuration

📅 Schedule: Branch creation - "before 8am on monday" in timezone Asia/Tokyo, 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. View repository job log here.

[coderabbitai]

Important

Auto Review Skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

---

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit-tests for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit tests for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.