fix: Update GitHub Actions

[vtjl10]

---

Description

• Upgraded the actions/checkout step from v4 to v5.

---

Summary by CodeRabbit

• Chores
  • Updated internal workflows to use the latest version of the checkout action for improved reliability. No changes to application features or user experience.

[coderabbitai]

Walkthrough

The GitHub Actions workflows for benchmarks and continuous integration were updated to use version 5 of the actions/checkout action, replacing version 4. No other workflow steps or configurations were modified.

Changes

Files	Change Summary
.github/workflows/benchmarks.yml, .github/workflows/ci.yml	Updated actions/checkout from v4 to v5 in workflow files

Poem

A hop and a skip, our workflows renew,
With checkout v5, we leap right through!
No extra steps, just fresher code,
On CI and benchmarks, down the road.
🐇✨

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

.github/workflows/ci.yml (1)

12-12: Pin the action to a specific commit SHA to harden the workflow

Using a moving tag (actions/checkout@v5) leaves you vulnerable to a compromised upstream release. GitHub recommends pinning third-party actions to a full commit hash instead:

-      - uses: actions/checkout@v5
+      - uses: actions/checkout@v5
+        # Pin for supply-chain safety – replace with the latest v5 SHA
+        # - uses: actions/checkout@v5.1.0  # example

Also verify your self-hosted (if any) runners have Node 20, as checkout@v5 runs on the Node 20 runtime.

.github/workflows/benchmarks.yml (1)

14-14: Repeat the security hardening here

Same remark: pin actions/checkout@v5 to a commit SHA to avoid supply-chain risk and ensure reproducible builds.

-      - uses: actions/checkout@v5
+      - uses: actions/checkout@v5
+        # Consider pinning: actions/checkout@v5.1.0  (or explicit SHA)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0e4c40f and 2b91466.

📒 Files selected for processing (2)

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