chore(deps): update dependency golangci-lint to v1.60.3

[renovate]

This PR contains the following updates:

Package	Update	Change
golangci-lint	patch	1.60.1 -> 1.60.3

---

Release Notes

golangci/golangci-lint (golangci-lint)

v1.60.3

Compare Source

1. Updated linters
   • gosec: from 81cda2f to ab3f6c1 (fix G115 false positives)
2. Misc.
   • Check that the Go version use to build is greater or equals to the Go version of the project

v1.60.2

Compare Source

1. Updated linters

• gofmt: update to HEAD (go1.22)
• gofumpt: from 0.6.0 to 0.7.0
• gosec: fix G602 analyzer
• gosec: from 5f0084e to 81cda2f (adds G115, G405, G406, G506, G507)
• staticcheck: from 0.5.0 to 0.5.1
• staticcheck: propagate Go version
• wrapcheck: from 2.8.3 to 2.9.0
• ⚠️ exportloopref: deprecation

---

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 was generated by Mend Renovate. View the repository job log.

[coderabbitai]

Walkthrough

The change involves updating the version of golangci-lint in the .tool-versions file from 1.60.1 to 1.60.3. This update reflects a minor version increment, which typically includes bug fixes, performance improvements, or new features relevant to linting Go code. The update ensures the linting process utilizes the latest version of the tool.

Changes

File	Change Summary
.tool-versions	Updated golangci-lint from 1.60.1 to 1.60.3

Poem

🐇 In the code where rabbits roam,
A linting tool finds its home.
With a hop and a skip, it’s updated anew,
To catch all the bugs and make things true.
So let’s cheer for the changes, a joyful delight,
As our Go code shines ever so bright! 🌟

---

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 testing code 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 testing code 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 testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

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 an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

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

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between aedfbc1 and 6507e77.

Files selected for processing (1)

• .tool-versions (1 hunks)

Files skipped from review due to trivial changes (1)

• .tool-versions