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

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
actions/checkout	action	major	v4 -> v5

---

Release Notes

actions/checkout (actions/checkout)

v5

Compare Source

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC).

🚦 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.

[codegen-sh]

Found 0 critical and 1 important issue. Please review my note below.

Issue (Important): actions/checkout@v5 requires Node.js 24 and may break on self-hosted runners

Context:
This PR bumps actions/checkout from v4 to v5 across multiple workflows (.github/workflows/auto-release.yml, pre-commit.yml, release.yml, test.yml, ty.yml). Checkout v5 runs on Node.js 24. If any of your self-hosted runner pools (e.g., labels ubuntu-latest-8, ubuntu-latest-16, ubuntu-latest-32) aren’t updated to a runner version that supports Node 24, the checkout step will fail to initialize at runtime, causing CI failures.

Why this matters:

• It’s a runtime compatibility risk on self-hosted runners that lag behind GitHub’s runner updates.
• Failures would occur immediately when the action loads, blocking all dependent jobs.

Actionable recommendation:

• Verify that all self-hosted runner groups used by these jobs support Node 24.
• If not yet upgraded, keep actions/checkout at v4 for those specific jobs until the runner pools are updated.
• After verification/upgrade, proceed with v5.

Example targeted rollback suggestions (apply only where runners aren’t Node 24–ready):

Auto Release:

 - uses: actions/checkout@v4 with: fetch-depth: 0

Pre-commit:

 uses: actions/checkout@v4

Release (build job):

 - uses: actions/checkout@v4 with: fetch-depth: 0 ref: ${{ inputs.release-tag || github.event.pull_request.head.ref || github.ref }}

Release (release job):

 - uses: actions/checkout@v4

Tests – unit-tests job:

 - uses: actions/checkout@v4 with: fetch-depth: 0 ref: ${{ github.event.pull_request.head.sha }}

Tests – codemod-tests job:

 - uses: actions/checkout@v4 with: ref: ${{ github.event.pull_request.head.sha }}

Tests – integration-tests job:

 - uses: actions/checkout@v4 with: ref: ${{ github.event.pull_request.head.sha }}

Once all self-hosted runners are confirmed to support Node 24, you can safely move each job back to actions/checkout@v5.

🔍 View my analysis: https://codegen.com/agent/trace/77574