ci: bump actions/checkout version

[iiio2]

Summary by CodeRabbit

• Chores

  • Upgraded CI workflows to use newer actions and package manager versions (checkout and package-manager setup). Build and lint steps remain unchanged. No user-facing changes.

• Tests

  • Test workflow updated to use the latest checkout and package-manager tooling; test execution and coverage remain unchanged.

[coderabbitai]

Walkthrough

Updated GitHub Actions workflows: both .github/workflows/ci.yml and .github/workflows/test.yml update actions/checkout from v4 to v5; additionally .github/workflows/test.yml updates pnpm/action-setup v2→v4 and pnpm version 9→10. No control flow or step logic changed.

Changes

Cohort / File(s)	Summary of Changes
CI & Test workflows .github/workflows/ci.yml, .github/workflows/test.yml	actions/checkout bumped v4 → v5. In test.yml also bumped pnpm/action-setup v2 → v4 and pnpm v9 → v10. No other steps or control flow altered.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

I nudge the pipeline with a gentle hop,
From v4 to v5—just one small swap.
PNPM peeks up, updated to ten,
Workflows refreshed, then back again.
A rabbit claps: quick patch, then on we hop! 🥕✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title "ci: bump actions/checkout version" is concise and accurately describes the primary change in the changeset (upgrading actions/checkout from v4 to v5 in CI workflows), so it conveys the main developer intent and is clear for a reviewer scanning history. It does not misrepresent the changes, though the test workflow also includes pnpm-related bumps which are secondary to the stated title.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/bump-actions-checkout

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9fca1cb and 9d18832.

📒 Files selected for processing (1)

• .github/workflows/test.yml (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• .github/workflows/test.yml

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: ci

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

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

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
v4	Ready	Preview	Comment	Sep 22, 2025 5:17pm

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

.github/workflows/ci.yml (1)

20-20: Optional: add explicit permissions and pin to commit SHA for supply-chain hardening.

• Explicitly grant the least token permission required by checkout:

# at jobs.ci level
permissions:
  contents: read

• Pin the action to the v5.0.0 commit to avoid tag-move risk:

-      - uses: actions/checkout@v5
+      - uses: actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8

Checkout’s README recommends contents: read, and GitHub’s security guidance recommends pinning to a full commit SHA. (github.com)

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 5a971c6 and 9fca1cb.

📒 Files selected for processing (2)

• .github/workflows/ci.yml (1 hunks)
• .github/workflows/test.yml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: ci
• GitHub Check: test

🔇 Additional comments (2)

.github/workflows/ci.yml (1)

20-20: Upgrade to actions/checkout v5 looks good; verify runner compatibility.
V5 runs on Node 24 and requires Actions Runner v2.327.1 or newer; GitHub-hosted ubuntu-latest is fine, but if any self-hosted runners are used, ensure they meet this minimum. (github.com)

.github/workflows/test.yml (1)

14-14: Upgrade to actions/checkout v5 looks good; verify runner compatibility.
Same note: v5 requires Actions Runner v2.327.1+. Fine on GitHub-hosted; confirm if any self-hosted runners participate in this workflow. (github.com)