ci: bump golangci-lint-action to v8

[eeemmmmmm]

Maintenance update to golangci-lint-action@v8 to align with the current best practices; nothing else modified. Refer to v8.0.0 release notes for details.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
warden-help-center	⬜️ Ignored (Inspect)	Visit Preview		Jun 2, 2025 6:52pm

[coderabbitai]

📝 Walkthrough

Walkthrough

The GitHub Actions workflows for several projects were updated to use version 8 of the golangci-lint-action instead of version 7. No other workflow steps, arguments, or configurations were changed across the affected workflow files.

Changes

Files	Change Summary
.github/workflows/faucet.yml .github/workflows/go-client.yml .github/workflows/keychain-sdk.yml .github/workflows/shield.yml .github/workflows/soliditygen.yml .github/workflows/wardend.yaml .github/workflows/wardenkms.yml	Updated golangci-lint-action from version 7 to version 8 in the lint job. No other changes made.

Possibly related PRs

• warden-protocol/wardenprotocol#981: Updates golangci-lint-action in workflows to a newer version and also upgrades setup-go and Go versions, similar in scope to this PR.

Suggested reviewers

• jlehtimaki
• backsapc

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c7f8349 and bcf2240.

📒 Files selected for processing (7)

• .github/workflows/faucet.yml (1 hunks)
• .github/workflows/go-client.yml (1 hunks)
• .github/workflows/keychain-sdk.yml (1 hunks)
• .github/workflows/shield.yml (1 hunks)
• .github/workflows/soliditygen.yml (1 hunks)
• .github/workflows/wardend.yaml (1 hunks)
• .github/workflows/wardenkms.yml (1 hunks)

🔇 Additional comments (7)

.github/workflows/shield.yml (1)

25-25: Approve golangci-lint-action bump to v8
This updates the lint action to v8, consistent with other workflows and aligns with the upstream release.

.github/workflows/soliditygen.yml (1)

25-25: Approve golangci-lint-action bump to v8
The lint step now uses golangci-lint-action@v8, matching the version upgrade across all projects.

.github/workflows/wardend.yaml (1)

38-38: Approve golangci-lint-action bump to v8
The golangci-lint-action has been upgraded to v8, keeping configuration and args unchanged.

.github/workflows/keychain-sdk.yml (1)

25-25: Approve golangci-lint-action bump to v8
Lint job now references version 8 of the GitHub Action, consistent with the CI maintenance plan.

.github/workflows/go-client.yml (1)

25-25: Approve golangci-lint-action bump to v8
Upgraded the action to v8; no other changes to lint args or setup.

.github/workflows/faucet.yml (1)

39-39: Upgrade golangci-lint-action to v8
The lint job now uses golangci/golangci-lint-action@v8 as intended by this maintenance PR. No further configuration changes are necessary.

.github/workflows/wardenkms.yml (1)

33-33: Upgrade golangci-lint-action to v8
This update aligns the WardenKMS workflow with the other projects by bumping to golangci-lint-action@v8. Configuration remains consistent.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

‼️ IMPORTANT
Auto-reply has been disabled for this repository in the CodeRabbit settings. The CodeRabbit bot will not respond to your replies unless it is explicitly tagged.

• 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 explain this code block.
  • @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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 using 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 generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this 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.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

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.

[Pitasi]

from the release notes:

Requires golangci-lint version >= v2.1.0

i think we need to bump golangci-lint as well, and fix all the new linter problems

is this something you want to take care of @eeemmmmmm?

[eeemmmmmm]

give me some time, I'll do everything, thank you

[Pitasi]

superseeded by #1631