chore: update GitHub actions in CI workflows

[ozrg]

Updates actions/checkout@v4 to actions/checkout@v5 across CI workflows.
Upgrade to actions/checkout@v5 for improved performance and stability.

Reference:
Latest version: https://github.com/actions/checkout/releases/tag/v5.0.0

Summary by CodeRabbit

• Chores
  • Upgraded the release automation to use the latest underlying checkout action for improved reliability and compatibility with the CI environment.
  • Strengthens long-term maintenance of the release pipeline without altering build outputs.
  • No user-facing changes; application behavior and interface remain the same.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 22cb6bc

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Walkthrough

The Release GitHub Actions workflow was updated to use actions/checkout@v5 instead of actions/checkout@v4 in the checkout step. No other workflow changes were made.

Changes

Cohort / File(s)	Summary
CI workflow .github/workflows/release.yml	Bump checkout action from actions/checkout@v4 to actions/checkout@v5 in the Release workflow.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A hop, a skip, a version flip—
I nudge the gears with gentle grip.
From four to five, the checkout sings,
The release path trims its wings.
Thump-thump, I sign with whiskered cheer:
“Ship it swift—same trail, new gear!” 🐇✨

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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.
  • 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.
• 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

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

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

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

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• 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/release.yml (2)

19-21: Optionally pin checkout to a commit SHA for supply-chain hardening

If your org pins third-party actions, consider locking to the v5.0.0 commit with a comment for readability.

-        uses: actions/checkout@v5
+        # v5.0.0
+        uses: actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8

Reference: actions/checkout v5.0.0 commit. (github.com)

---

19-21: Consider full fetch if release tooling needs tags/history

Changesets and some release flows benefit from access to full history and tags. If you’ve seen shallow-clone quirks, set fetch-depth: 0.

       - name: Checkout Repo
-        uses: actions/checkout@v5
+        uses: actions/checkout@v5
+        with:
+          fetch-depth: 0

The checkout README shows this pattern for “Fetch all history for all tags and branches.” (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 55b9511 and 22cb6bc.

📒 Files selected for processing (1)

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

🔇 Additional comments (2)

.github/workflows/release.yml (2)

19-21: Upgrade to actions/checkout@v5 looks good

v5 switches the action runtime to Node.js 24 and requires Actions Runner ≥ v2.327.1. Using ubuntu-latest on GitHub-hosted runners already satisfies this, so this step should work as-is. (github.com)

---

19-21: All workflows use actions/checkout@v5 and no self-hosted runners detected
Verified that every workflow in .github/workflows uses actions/checkout@v5 (release.yml line 20) and there are no self-hosted runner references. No further changes needed.