chore(deps): update actions/checkout action to v5.0.1

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
actions/checkout	action	patch	v5.0.0 -> v5.0.1

---

Release Notes

actions/checkout (actions/checkout)

v5.0.1

Compare Source

What's Changed

• Port v6 cleanup to v5 by @​ericsciple in #​2301

Full Changelog: actions/checkout@v5...v5.0.1

---

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 becomes conflicted, or you tick the rebase/retry checkbox.

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

---

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

---

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

[github-actions]

Renovate PR Review Results

⚖️ Safety Assessment: ✅ Safe

🔍 Release Content Analysis

• Minor maintenance update: This is a patch release with a single change focused on auth configuration cleanup
• No breaking changes: The update only ports cleanup logic from v6 to v5 for better compatibility
• Improved stability: Prevents potential failures when using multiple checkout actions in the same job
• Backward compatibility: Maintains full compatibility with existing configurations
• New feature: Introduces ACTIONS_CHECKOUT_SKIP_V6_CLEANUP environment variable for edge cases

🎯 Impact Scope Investigation

• 9 total usages: actions/checkout is used across 4 workflow files (ci.yml, claude-renovate-review.yml, github-actions-lint.yml, release-please.yml)
• Consistent configuration: All usages follow the same pattern with persist-credentials: false
• No custom checkout options: No complex configurations that could be affected by the cleanup logic
• No dependency conflicts: The composite action in .github/actions/setup doesn't use checkout internally

💡 Recommended Actions

• ✅ Safe to merge immediately: No code changes or manual intervention required
• Standard workflow testing: The change should be verified through normal CI pipeline execution
• Monitor first runs: Watch the first few workflow executions after merge for any unexpected behavior
• No configuration changes needed: All existing persist-credentials: false settings remain appropriate

🔗 Reference Links

• Release Notes v5.0.1
• PR #2301 - Port v6 cleanup to v5
• Compare v5.0.0...v5.0.1

Generated by koki-develop/claude-renovate-review