chore(deps): update actions/checkout action to v6

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
actions/checkout	action	major	v5 -> v6
actions/checkout	action	major	v5.0.1 -> v6.0.1

---

Release Notes

actions/checkout (actions/checkout)

v6

Compare Source

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 86.88%. Comparing base (1962e01) to head (7b7e476).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #587   +/-   ##
=======================================
  Coverage   86.88%   86.88%           
=======================================
  Files          12       12           
  Lines        1761     1761           
=======================================
  Hits         1530     1530           
  Misses        155      155           
  Partials       76       76           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[claude]

Code Review: Update actions/checkout to v6

Overview

This PR updates actions/checkout from v5 to v6 across three workflow files. This is a major version upgrade generated by Renovate.

Analysis

✅ Code Quality & Best Practices

• Consistency: The update is applied consistently across all three workflow files (.github/workflows/build.yml, claude-code-review.yml, and claude.yml)
• Version pinning: Good practice maintaining minor version pins (v6.0.1 in build.yml, v6 in the others) - though consistency would be improved by using the same pinning strategy across all workflows

⚠️ Potential Issues

1. Major Version Upgrade: This is a major version bump (v5 → v6), which typically indicates breaking changes. The PR description doesn't include release notes for v6, making it difficult to assess compatibility impact.

2. Inconsistent version pinning:

   • build.yml: Uses v6.0.1 (specific minor version)
   • claude-code-review.yml and claude.yml: Use v6 (floating on latest v6.x)
   • Recommendation: Use consistent pinning strategy. Either pin all to v6.0.1 or use v6 across all workflows.

3. Missing compatibility verification: The workflows use fetch-depth: 1 (shallow clone), which should be compatible, but without v6 release notes, we can't confirm there are no behavioral changes.

🔒 Security Considerations

• Low risk: GitHub Actions from the official actions org are generally trustworthy
• Consideration: Major version updates can introduce new security features or deprecate old patterns - reviewing the v6 changelog would be prudent

⚡ Performance Considerations

• Neutral impact: No expected performance impact from the diff itself
• actions/checkout v6 may include performance improvements, but this requires checking release notes

🧪 Test Coverage

• No test changes needed: This is a CI/CD infrastructure change
• Recommendation: Verify that CI passes successfully on this branch before merging
• The workflows themselves will test the new action version

📋 Recommendations

1. Before merging:

   • Review the actions/checkout v6 release notes to identify any breaking changes
   • Ensure CI checks pass on this PR
   • Verify that all three workflows execute successfully with v6

2. Consider: Standardize version pinning across all workflows:

   # Option A: Pin to specific minor version (more stable)
   uses: actions/checkout@v6.0.1
   
   # Option B: Float on v6.x (get patches automatically)
   uses: actions/checkout@v6

3. Renovate configuration: Since this is a major update, it correctly requires manual review (not auto-merged per renovate.json rules). This is appropriate given the potential for breaking changes.

Verdict

✅ Approve with caveats: The code changes are clean and consistent, but verify CI passes and ideally review the v6 changelog before merging. The upgrade itself is straightforward, but major versions warrant additional verification.

---

Reviewed by Claude Code