ci: updated github actions to latest

[fahimfaisaal]

Description

Brief description of what this PR does.

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Performance improvement
• Refactoring

Changes Made

updated github actions to latest for checkout and setup go

Testing

• Tests pass locally
• Added new tests for the changes
• Updated existing tests if needed

Performance Impact

• No performance impact
• Performance improvement
• Potential performance regression (explain below)

Checklist

• Code follows the project's style guidelines
• Self-review of code completed
• Code is commented where necessary
• Documentation updated if needed
• No new warnings or errors introduced

Related Issues

Fixes #(issue number)

Additional Notes

Any additional information that reviewers should know.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

GitHub Actions workflow versions upgraded from v4 to v6 for checkout and setup-go actions. A new "Install dependencies" step executing go mod download is introduced in test and bench jobs. A formatting change collapses a multi-line function call to single-line in a test file.

Changes

Cohort / File(s)	Summary
CI Workflow Updates \.github/workflows/ci.yml	Bumped actions/checkout from v4 to v6 and actions/setup-go from v4 to v6 in test and bench jobs. Added "Install dependencies" step running go mod download before test execution.
Test File Formatting config_test.go	Collapsed multi-line loadConfigs(4) call to single-line format; no functional changes.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~5–10 minutes

• Straightforward version bumps applied consistently across workflow steps
• Addition of go mod download step is a standard dependency installation practice
• Config test formatting change is purely cosmetic with no logic alterations

Possibly related PRs

• chore: included dependency cache layer with ci workflow #50: Modifies the same CI workflow (.github/workflows/ci.yml), updating actions/setup-go and actions/checkout versions with similar dependency handling changes.
• chore: seperate test and bench job to accelerate the ci process #52: Updates the same CI workflow file to restructure Go environment setup and test/bench job configuration with custom action changes.

Poem

🐰 A rabbit hops through workflows bright,
Updating actions—v6 in sight!
Dependencies downloaded with care,
Tests now faster, code runs fair! ✨

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch ci/upgraded-actions

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 829878d and 89a21d5.

📒 Files selected for processing (2)

• .github/workflows/ci.yml (2 hunks)
• config_test.go (1 hunks)

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".