Skip to content

Bump actions/checkout from 4 to 6 in the github-actions group#5

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/github-actions-76468cb07f
Open

Bump actions/checkout from 4 to 6 in the github-actions group#5
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/github-actions-76468cb07f

Conversation

@dependabot
Copy link
Copy Markdown

@dependabot dependabot Bot commented on behalf of github Jun 1, 2026

Bumps the github-actions group with 1 update: actions/checkout.

Updates actions/checkout from 4 to 6

Release notes

Sourced from actions/checkout's releases.

v6.0.0

What's Changed

Full Changelog: actions/checkout@v5.0.0...v6.0.0

v6-beta

What's Changed

Updated persist-credentials to store the credentials under $RUNNER_TEMP instead of directly in the local git config.

This requires a minimum Actions Runner version of v2.329.0 to access the persisted credentials for Docker container action scenarios.

v5.0.1

What's Changed

Full Changelog: actions/checkout@v5...v5.0.1

v5.0.0

What's Changed

⚠️ Minimum Compatible Runner Version

v2.327.1
Release Notes

Make sure your runner is updated to this version or newer to use this release.

Full Changelog: actions/checkout@v4...v5.0.0

v4.3.1

What's Changed

Full Changelog: actions/checkout@v4...v4.3.1

v4.3.0

What's Changed

... (truncated)

Changelog

Sourced from actions/checkout's changelog.

Changelog

v6.0.2

v6.0.1

v6.0.0

v5.0.1

v5.0.0

v4.3.1

v4.3.0

v4.2.2

v4.2.1

v4.2.0

v4.1.7

v4.1.6

... (truncated)

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

Summary by CodeRabbit

  • Chores
    • Updated CI/CD infrastructure dependencies to maintain build system stability and security.

Bumps the github-actions group with 1 update: [actions/checkout](https://github.com/actions/checkout).


Updates `actions/checkout` from 4 to 6
- [Release notes](https://github.com/actions/checkout/releases)
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
- [Commits](actions/checkout@v4...v6)

---
updated-dependencies:
- dependency-name: actions/checkout
  dependency-version: '6'
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: github-actions
...

Signed-off-by: dependabot[bot] <support@github.com>
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Jun 1, 2026

Review Change Stack

📝 Walkthrough

Walkthrough

The Rust CI workflow is updated to use GitHub Actions checkout v6 instead of v4, replacing the action reference in the "Checkout sources" step.

Changes

CI Workflow Update

Layer / File(s) Summary
Checkout Action Version Bump
.github/workflows/rust.yml
The checkout action is updated from actions/checkout@v4 to actions/checkout@v6 in the CI workflow.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A version bump, so small and neat,
From four to six, the update's complete,
Checkout now runs with fresher grace,
Let's pull those sources to the right place! 🎯

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately describes the main change: upgrading actions/checkout from version 4 to 6 in the github-actions dependency group, which matches the file changes in .github/workflows/rust.yml.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch dependabot/github_actions/github-actions-76468cb07f

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.github/workflows/rust.yml:
- Around line 36-37: Update the "📥 Checkout sources" step that currently uses
actions/checkout@v6 to hard-pin to the v6.0.2 commit SHA and disable credential
persistence; specifically replace the mutable reference actions/checkout@v6 with
the exact v6.0.2 commit SHA and add persist-credentials: false to that checkout
step so the workflow no longer retains authenticated git credentials for later
steps.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 0822a029-ec60-4020-9ac8-f6584460f695

📥 Commits

Reviewing files that changed from the base of the PR and between 99e7f37 and f96ee84.

📒 Files selected for processing (1)
  • .github/workflows/rust.yml

Comment on lines 36 to +37
- name: 📥 Checkout sources
uses: actions/checkout@v4
uses: actions/checkout@v6
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major | ⚡ Quick win

🧩 Analysis chain

🌐 Web query:

What is the official commit SHA for the latest stable actions/checkoutv6 release, and does its README documentpersist-credentials default behavior and security implications?

💡 Result:

The latest stable release of actions/checkout as of June 1, 2026, is v6.0.2 [1]. The commit SHA for v6.0.2 is 11bd70f011116c478a87693246313203f56b7c5e. Regarding persist-credentials: - The README explicitly documents the persist-credentials input [2][3]. - Its default behavior is true, meaning the action configures the authentication token (or SSH key) with the local git config to enable authenticated git commands [2][3]. - In v6, the action has been updated to improve security: instead of storing credentials directly in .git/config, they are now stored in a separate file under $RUNNER_TEMP [2][4][3]. - While the README highlights this as "improved credential security" [2][3], it acknowledges that the token remains available to subsequent steps in the job [2]. Users who wish to disable this behavior can explicitly set persist-credentials: false [2][3].

Citations:


Pin actions/checkout and disable persisted credentials

Line 37 uses mutable actions/checkout@v6, which weakens supply-chain guarantees; hard-pin to the v6.0.2 commit SHA. Also disable credential persistence since this workflow doesn’t need authenticated git credentials for later steps.

🔐 Proposed hardening patch
       - name: 📥 Checkout sources
-        uses: actions/checkout@v6
+        uses: actions/checkout@11bd70f011116c478a87693246313203f56b7c5e
+        with:
+          persist-credentials: false
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- name: 📥 Checkout sources
uses: actions/checkout@v4
uses: actions/checkout@v6
- name: 📥 Checkout sources
uses: actions/checkout@11bd70f011116c478a87693246313203f56b7c5e
with:
persist-credentials: false
🧰 Tools
🪛 zizmor (1.25.2)

[warning] 36-37: credential persistence through GitHub Actions artifacts (artipacked): does not set persist-credentials: false

(artipacked)


[error] 37-37: unpinned action reference (unpinned-uses): action is not pinned to a hash (required by blanket policy)

(unpinned-uses)

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.github/workflows/rust.yml around lines 36 - 37, Update the "📥 Checkout
sources" step that currently uses actions/checkout@v6 to hard-pin to the v6.0.2
commit SHA and disable credential persistence; specifically replace the mutable
reference actions/checkout@v6 with the exact v6.0.2 commit SHA and add
persist-credentials: false to that checkout step so the workflow no longer
retains authenticated git credentials for later steps.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants