fix: align golang lint version and download dependencies before running

[WasinWatt]

Description

Closes: #XXXX

---

Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow-up issues.

I have...

• included the correct type prefix in the PR title, you can find examples of the prefixes below:
• confirmed ! in the type prefix if API or client breaking change
• targeted the correct branch
• provided a link to the relevant issue or specification
• reviewed "Files changed" and left comments if necessary
• included the necessary unit and integration tests
• updated the relevant documentation or specification, including comments for documenting Go code
• confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

• confirmed the correct type prefix in the PR title
• confirmed all author checklist items have been addressed
• reviewed state machine logic, API design and naming, documentation is accurate, tests and test coverage

Summary by CodeRabbit

• Chores
  • Updated the build workflow to use a newer version of golangci-lint and improved the installation process for dependencies.

[coderabbitai]

Walkthrough

The GitHub Actions workflow for the "Basic Checks" job was updated to use golangci-lint v1.62.0 instead of v1.61.0. The installation process was restructured into three separate steps: clearing the Go module cache, downloading dependencies, and installing golangci-lint. No other workflow steps were changed.

Changes

Cohort / File(s)	Change Summary
GitHub Actions Workflow Update .github/workflows/build-release.yml	Updated golangci-lint to v1.62.0, split the install step into cache clearing, dependency download, and installation.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~7 minutes

Poem

A rabbit hops through YAML fields,
Clearing caches, dependencies it wields.
With linting tools now up to date,
Bugs and errors meet their fate.
Three steps now where once was one—
Release builds brighter, swiftly done!
🐇✨

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/golangci-on-release

---

🪧 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>, please review it.
  • Explain this complex logic.
  • 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 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 generate unit tests to generate unit tests for 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.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• 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/schema.v2.json

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

🧹 Nitpick comments (1)

.github/workflows/build-release.yml (1)

22-27: Re-consider clearing the module cache – it slows the job down

go clean -modcache wipes the whole download cache, so every subsequent go mod download step has to fetch the world from scratch on every run. Because GitHub runners are ephemeral you already start from a cold cache each time, so this call offers no benefit but increases network time.

-      - name: Clear module cache
-        run: go clean -modcache
-
-      - name: Download dependencies
-        run: go mod download
+      # Save a few seconds per run by relying on the implicit empty cache.
+      - name: Download dependencies
+        run: go mod download

If the intention is to guarantee a pristine go.sum, consider instead enabling the official actions/cache step to persist the module cache between jobs – it will cut minutes off larger matrices.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c87b38d and 4243b72.

📒 Files selected for processing (1)

• .github/workflows/build-release.yml (2 hunks)

🔇 Additional comments (2)

.github/workflows/build-release.yml (2)

13-13: GolangCI-Lint bumped to v1.62.0 – looks good
Pinning the linter to the latest release keeps the ruleset in sync with upstream Go. No issues spotted.

---

28-30: Install step is fine – binary will be on PATH after setup-go
go install ...@${GOLANGCI_LINT_VERSION} is the recommended way since Go 1.17+. No further action needed.