Increase GitHub Action checkout version to v5

[mulkieran]

Related stratis-storage/project#807

Summary by CodeRabbit

• Chores
  • Updated CI workflow to use the latest checkout action and disabled credential persistence, improving pipeline security and reliability.
  • No user-facing changes; application behavior and features remain unaffected.

[coderabbitai]

Walkthrough

Updated .github/workflows/main.yml by upgrading actions/checkout from v4 to v5 in two steps and adding persist-credentials: false to each checkout step. No other workflow structure or commands changed.

Changes

Cohort / File(s)	Summary of Changes
GitHub Actions Workflow .github/workflows/main.yml	Bumped actions/checkout from v4 to v5 in two steps; added with: persist-credentials: false to both checkout steps; no other modifications.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related issues

• Increase GitHub Action checkout version to v5 project#807 — Matches the same workflow change: upgrading actions/checkout to v5 and setting persist-credentials to false.

Poem

A hop, a skip, a version jump—how neat!
I checked out v5 with tidy, cautious feet.
Credentials tucked, no crumbs to trace,
The pipeline thumps at a steady pace.
Thump-thump hooray—automation’s sweet! 🐇✨

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

---

🪧 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 (1)

.github/workflows/main.yml (1)

35-37: actions/checkout@v5 + persist-credentials: false — upgrade verified; no legacy checkout, no submodules, no history-dependent tools detected

Scan results:

• No other actions/checkout@v1|2|3|4 usages in .github
• No .gitmodules file present
• No setuptools-scm, use_scm_version, or git describe/rev-parse/log calls found

Optional hardening recommendations:

• Pin the checkout action to a specific commit SHA (or enable Dependabot) to reduce supply-chain risk.
• If you ever need full git history or submodule support, add fetch-depth: 0 and/or submodules: true.

📜 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 5e65a5a and d52249e.

📒 Files selected for processing (1)

• .github/workflows/main.yml (2 hunks)

🔇 Additional comments (1)

.github/workflows/main.yml (1)

69-71: Consistent upgrade in the second job — LGTM

The second checkout is also correctly bumped to v5 with credentials persistence disabled. Same optional notes about pinning and history/submodules apply if relevant.