chore(deps): update actions/checkout action to v4.3.1

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
actions/checkout	action	patch	v4.3.0 → v4.3.1

---

Release Notes

actions/checkout (actions/checkout)

v4.3.1

Compare Source

What's Changed

• Port v6 cleanup to v4 by @​ericsciple in #​2305

Full Changelog: actions/checkout@v4...v4.3.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 patch update: v4.3.0 → v4.3.1 with backward compatibility maintained
• Auth configuration cleanup: Ports v6-beta improvements to v4 to prevent potential failures when multiple checkouts occur in the same job
• No breaking changes: All existing configurations and parameters remain functional
• Improved reliability: Fixes edge cases with multiple repository checkouts within a single workflow job
• Optional mitigation: Users can skip new cleanup logic via ACTIONS_CHECKOUT_SKIP_V6_CLEANUP environment variable if needed

🎯 Impact Scope Investigation

• Usage locations: actions/checkout@v4.3.0 is used in 6 locations across 3 workflow files:
  • .github/workflows/ci.yml:16,29 (lint and build jobs)
  • .github/workflows/github-actions-lint.yml:27,39,53 (actionlint, ghalint, zizmor jobs)
  • .github/workflows/release-please.yml:39 (release job)
• Configuration consistency: All usages employ persist-credentials: false for security
• No multiple checkouts: Each job uses only one checkout step, so the primary improvement (multiple checkout reliability) doesn't directly impact current workflows
• No dependency conflicts: Update only affects GitHub Actions workflow execution, not project dependencies

💡 Recommended Actions

• Immediate merge: Safe to merge without any code modifications required
• No configuration changes needed: Existing workflow configurations will continue working as expected
• Monitor workflow execution: Verify workflows run successfully after merge (standard practice)
• Future benefit: Improved reliability foundation for any future workflows that might need multiple checkouts

🔗 Reference Links

• Release notes
• Pull Request #2305

Generated by koki-develop/claude-renovate-review