Increase GitHub Action checkout version to v5

[mulkieran]

Related stratis-storage/project#807

Summary by CodeRabbit

• Chores
  • Updated CI workflows to use the latest checkout action version for improved reliability.
  • Disabled credential persistence in checkout steps to enhance security in pipeline runs.
  • No changes to product features or behavior; builds and deployments remain unchanged.

[coderabbitai]

Walkthrough

Updated GitHub Actions workflows to use actions/checkout@v5 and set persist-credentials: false in checkout steps for main.yml and push.yml. No other workflow logic or steps were modified.

Changes

Cohort / File(s)	Summary of Changes
GitHub Actions workflows .github/workflows/main.yml, .github/workflows/push.yml	Bumped actions/checkout from v4 to v5; added with: persist-credentials: false to checkout steps; no other step or logic changes.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related issues

• Increase GitHub Action checkout version to v5 project#807 — Matches the upgrade to actions/checkout v5 and disabling credential persistence done in these workflows.

Poem

I hop through YAML fields so bright,
Nudging checkout to the latest light.
No tokens linger, clean and clear,
v5 now leads without a fear.
Thump-thump! My paws approve the run—
Secure and swift, the job is done. 🐇✨

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 (2)

.github/workflows/main.yml (1)

91-93: Second checkout step likewise updated — consistent and correct

Mirrors the earlier step. No issues spotted. If you ever need tags or full history for Makefile/package tasks, consider fetch-depth: 0 on checkout (not required by current workflow).

.github/workflows/push.yml (1)

36-40: Upgrade to actions/checkout@v5 with explicit persist-credentials: false — aligned with best practices

Use of path: into-dbus-python remains correct, and subsequent working-directory steps already point there. Disabling credential persistence is appropriate since this job only diffs locally and doesn’t push.

Optional hardening ideas (no change required):

• Pin actions/checkout to a specific commit SHA for supply-chain hardening.
• Add top-level permissions: contents: read to be explicit about least privilege.

📜 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 7c38ca4 and dd689d3.

📒 Files selected for processing (2)

• .github/workflows/main.yml (2 hunks)
• .github/workflows/push.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). (1)

• GitHub Check: monkeytype

🔇 Additional comments (1)

.github/workflows/main.yml (1)

49-51: All checkout steps updated to v5 with credentials not persisted — approved
Verification confirms:

• Every actions/checkout invocation in .github/workflows is at @v5 with persist-credentials: false
• No steps run git push|fetch|pull that would need an authenticated token
• No submodule checkouts that would require credentials

Safe to merge.