chore: use go module cache

[crhntr]

No description provided.

[claude]

PR Review: Enable Go Module Caching in GitHub Actions

Summary

This PR adds cache: true to the actions/setup-go@v6 step in the GitHub Actions workflow, enabling automatic caching of Go module dependencies.

✅ Positive Aspects

Performance Improvement

• This change will significantly speed up CI builds by caching Go modules between runs
• The actions/setup-go@v6 action handles cache key generation automatically based on go.sum, which is the best practice
• No additional configuration needed - the action manages cache invalidation when dependencies change

Code Quality

• Minimal, focused change that does one thing well
• Aligns with GitHub Actions best practices for Go projects
• No breaking changes or side effects

📝 Minor Observation

Typo in PR Title
The PR title has a typo: "use go module cachd" should be "use go module cache"

✅ Security & Testing

• Security: No security concerns - this is a standard GitHub Actions feature
• Testing: The change will be validated when the workflow runs on this PR itself
• No additional tests needed: This is infrastructure configuration, not application code

🎯 Recommendation

LGTM with typo fix - This is a solid improvement to the CI pipeline. Consider fixing the typo in the PR title before merging.

Impact: Faster CI runs, reduced GitHub Actions minutes usage, better developer experience.

---

🤖 Review generated with Claude Code

[Copilot]

Pull request overview

This PR enables Go module caching in the GitHub Actions workflow to improve build performance by caching dependencies between workflow runs. The change adds the cache: true option to the actions/setup-go@v6 action, which will automatically cache Go modules and build artifacts based on the go.mod and go.sum files.

Key Change:

• Enabled built-in caching for the setup-go action in the CI workflow

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[claude]

PR Review: Enable Go Module Cache in GitHub Actions

Summary

This PR adds cache: true to the actions/setup-go@v6 action in the CI workflow, enabling automatic caching of Go modules and build artifacts.

Code Quality ✅

• Clean and minimal change: The modification is focused and follows best practices for GitHub Actions
• Idiomatic: Uses the built-in caching feature of setup-go@v6 rather than manual cache configuration
• Consistent with project goals: Aligns with the project's emphasis on simplicity and efficiency

Potential Issues ✅

No issues identified. The change is straightforward and low-risk.

Performance Considerations ✅ Positive Impact

This change will improve CI performance:

• Faster workflow runs: Go modules won't need to be re-downloaded on every run
• Build cache reuse: Compiled packages will be cached between runs
• Reduced network usage: Less bandwidth consumption from go.mod dependencies

Expected improvements:

• First run: Similar timing (cache miss)
• Subsequent runs: Significantly faster (potentially 30-50% reduction in setup time)

Security Concerns ✅

No security concerns:

• GitHub Actions cache is scoped to the repository
• Cache keys are automatically managed by setup-go@v6
• No credentials or sensitive data involved
• Cache isolation between branches is handled by GitHub

Test Coverage ✅

No tests needed for this infrastructure change. The workflow will validate itself on execution:

• If caching fails, the workflow falls back to downloading dependencies
• The existing test commands (go build ./... and go test -race -shuffle=on ./...) remain unchanged

Recommendation

LGTM - Approve and Merge ✅

This is a beneficial optimization with no downsides. The change:

• Reduces CI runtime
• Follows GitHub Actions best practices
• Maintains all existing test coverage
• Has zero impact on code functionality

Note: You may want to consider also caching in other workflows if they exist (.github/workflows/claude-code-review.yml, .github/workflows/claude.yml) for consistency, though that's outside the scope of this PR.