Skip to content

ci(deps): bump actions/checkout from 6.0.2 to 7.0.0 - #8780

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/actions/checkout-7.0.0
Open

ci(deps): bump actions/checkout from 6.0.2 to 7.0.0#8780
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/actions/checkout-7.0.0

Conversation

@dependabot

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

Copy link
Copy Markdown
Contributor

Bumps actions/checkout from 6.0.2 to 7.0.0.

Release notes

Sourced from actions/checkout's releases.

v7.0.0

What's Changed

New Contributors

Full Changelog: actions/checkout@v6.0.3...v7.0.0

v6.0.3

What's Changed

New Contributors

Full Changelog: actions/checkout@v6...v6.0.3

Changelog

Sourced from actions/checkout's changelog.

Changelog

v7.0.0

v6.0.3

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

... (truncated)

Commits

Summary by CodeRabbit

  • Chores
    • Updated repository automation workflows to use the newer pinned checkout action revision.
    • Maintained existing workflow steps, permissions, conditions, and behavior.

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

@dependabot dependabot Bot added area/ci-tooling Indicates the PR includes changes for CI or tooling ok-to-test Indicates a non-member PR verified by an org member that is safe to test. labels Jun 19, 2026
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

@coderabbitai

coderabbitai Bot commented Jun 19, 2026

Copy link
Copy Markdown
Contributor
📝 Walkthrough

Walkthrough

The pull request updates pinned actions/checkout commit references from v6.0.2 to v7.0.0 across 14 GitHub Actions workflow files. No other workflow logic, configuration, inputs, permissions, or steps are changed.

Suggested reviewers: nirshal, sjenning

🚥 Pre-merge checks | ✅ 11
✅ Passed checks (11 passed)
Check name Status Explanation
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.
Stable And Deterministic Test Names ✅ Passed Only .github/workflows YAML files changed; the diff contains no Ginkgo test title updates.
Test Structure And Quality ✅ Passed Only .github/workflows YAML files changed; no Ginkgo test code was touched, so the test-quality check is not applicable.
Topology-Aware Scheduling Compatibility ✅ Passed Only GitHub Actions checkout pins changed in workflow files; no manifests, controllers, or scheduling constraints were modified.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed PR only updates workflow YAML pins for actions/checkout; no new Ginkgo tests or network assumptions were added.
No-Weak-Crypto ✅ Passed Diff only bumps actions/checkout pins in workflows; no MD5/SHA1/DES/RC4/3DES/Blowfish/ECB, custom crypto, or secret comparisons were introduced.
Container-Privileges ✅ Passed Changed files are workflow-only checkout pin bumps; no touched manifest adds privileged/root/hostPID/hostNetwork settings.
No-Sensitive-Data-In-Logs ✅ Passed The PR only bumps actions/checkout pins; no added log statements or new exposure of tokens, secrets, or PII appears in the changed lines.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and concisely summarizes the primary change: upgrading actions/checkout from 6.0.2 to 7.0.0.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch dependabot/github_actions/actions/checkout-7.0.0

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

@openshift-ci

openshift-ci Bot commented Jun 19, 2026

Copy link
Copy Markdown
Contributor

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@openshift-ci
openshift-ci Bot requested review from Nirshal and sjenning June 19, 2026 01:07
@openshift-ci

openshift-ci Bot commented Jun 19, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dependabot[bot]
Once this PR has been reviewed and has the lgtm label, please assign jparrill for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

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/sync-community-fork.yaml:
- Around line 21-24: The checkout step is using a secret token
(COMMUNITY_FORK_TOKEN) without disabling credential persistence, which creates a
security risk of credential leakage through artifacts. Add persist-credentials:
false to the with section of the
actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 action to ensure
credentials are not persisted beyond the current job execution.
🪄 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: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: ab78103f-7108-4cd6-a936-c6e9c516a490

📥 Commits

Reviewing files that changed from the base of the PR and between 0096c63 and e1b55c2.

📒 Files selected for processing (14)
  • .github/workflows/codespell-reusable.yaml
  • .github/workflows/cpo-container-sync-reusable.yaml
  • .github/workflows/dependabot-commit-fix-reusable.yaml
  • .github/workflows/docs-build-reusable.yaml
  • .github/workflows/envtest-kube-reusable.yaml
  • .github/workflows/envtest-ocp-reusable.yaml
  • .github/workflows/gitlint-reusable.yaml
  • .github/workflows/gocacheprog-test-reusable.yaml
  • .github/workflows/lint-reusable.yaml
  • .github/workflows/reusable-claude-on-pr.yaml
  • .github/workflows/sync-community-fork.yaml
  • .github/workflows/test-reusable.yaml
  • .github/workflows/validate-cpo-overrides.yaml
  • .github/workflows/verify-reusable.yaml

Comment on lines +21 to 24
- uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
with:
fetch-depth: 0
token: ${{ secrets.COMMUNITY_FORK_TOKEN }}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🔴 Critical | ⚡ Quick win

Add persist-credentials: false to prevent credential leakage via artifacts.

This step checks out the repository using a secret token (COMMUNITY_FORK_TOKEN) but does not disable credential persistence. By default, GitHub Actions persists credentials to artifacts, creating a risk of secret exposure. Although this workflow requires the token for the subsequent push, credentials should not persist beyond the current job execution.

Per the coding guideline on least privilege and the static analysis warning, add persist-credentials: false to the checkout configuration.

🔐 Proposed fix to disable credential persistence
       - uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
         with:
           fetch-depth: 0
           token: ${{ secrets.COMMUNITY_FORK_TOKEN }}
+          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
- uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
with:
fetch-depth: 0
token: ${{ secrets.COMMUNITY_FORK_TOKEN }}
- uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
with:
fetch-depth: 0
token: ${{ secrets.COMMUNITY_FORK_TOKEN }}
persist-credentials: false
🧰 Tools
🪛 zizmor (1.25.2)

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

(artipacked)

🤖 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/sync-community-fork.yaml around lines 21 - 24, The
checkout step is using a secret token (COMMUNITY_FORK_TOKEN) without disabling
credential persistence, which creates a security risk of credential leakage
through artifacts. Add persist-credentials: false to the with section of the
actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 action to ensure
credentials are not persisted beyond the current job execution.

Sources: Coding guidelines, Linters/SAST tools

@dependabot
dependabot Bot force-pushed the dependabot/github_actions/actions/checkout-7.0.0 branch from e1b55c2 to 927a893 Compare July 2, 2026 07:07
Bumps [actions/checkout](https://github.com/actions/checkout) from 6.0.2 to 7.0.0.
- [Release notes](https://github.com/actions/checkout/releases)
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
- [Commits](actions/checkout@de0fac2...9c091bb)

---
updated-dependencies:
- dependency-name: actions/checkout
  dependency-version: 7.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/github_actions/actions/checkout-7.0.0 branch from 927a893 to f29ae8c Compare July 17, 2026 16:17

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
.github/workflows/dependabot-commit-fix-reusable.yaml (1)

25-29: 🔒 Security & Privacy | 🟠 Major | ⚡ Quick win

Avoid persisting write-capable checkout credentials.

Both workflows should disable credential persistence and authenticate only the required push without writing the token into .git/config.

  • .github/workflows/dependabot-commit-fix-reusable.yaml#L25-L29: use non-persisted authentication for the amended push to origin.
  • .github/workflows/sync-community-fork.yaml#L21-L24: use non-persisted authentication for the push to the community remote.
🤖 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/dependabot-commit-fix-reusable.yaml around lines 25 - 29,
Update the checkout steps in
.github/workflows/dependabot-commit-fix-reusable.yaml lines 25-29 and
.github/workflows/sync-community-fork.yaml lines 21-24 to disable persisted
credentials while retaining the required checkout authentication. Ensure each
workflow authenticates only its subsequent push to the appropriate remote
without writing the token into .git/config.

Sources: Path instructions, Linters/SAST tools

🤖 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/update-ci-job-registry.yaml:
- Around line 15-17: Update the actions/checkout step in the CI workflow to set
persist-credentials to false, preventing COMMUNITY_FORK_TOKEN from being stored
in git configuration. Then update the later git push step to authenticate
explicitly using the intended token while preserving its existing push behavior.

---

Outside diff comments:
In @.github/workflows/dependabot-commit-fix-reusable.yaml:
- Around line 25-29: Update the checkout steps in
.github/workflows/dependabot-commit-fix-reusable.yaml lines 25-29 and
.github/workflows/sync-community-fork.yaml lines 21-24 to disable persisted
credentials while retaining the required checkout authentication. Ensure each
workflow authenticates only its subsequent push to the appropriate remote
without writing the token into .git/config.
🪄 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: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: e9f75836-eb86-4de2-94e4-e55c6e5181dc

📥 Commits

Reviewing files that changed from the base of the PR and between e1b55c2 and f29ae8c.

📒 Files selected for processing (15)
  • .github/workflows/codespell-reusable.yaml
  • .github/workflows/cpo-container-sync-reusable.yaml
  • .github/workflows/dependabot-commit-fix-reusable.yaml
  • .github/workflows/docs-build-reusable.yaml
  • .github/workflows/envtest-kube-reusable.yaml
  • .github/workflows/envtest-ocp-reusable.yaml
  • .github/workflows/gitlint-reusable.yaml
  • .github/workflows/gocacheprog-test-reusable.yaml
  • .github/workflows/lint-reusable.yaml
  • .github/workflows/reusable-claude-on-pr.yaml
  • .github/workflows/sync-community-fork.yaml
  • .github/workflows/test-reusable.yaml
  • .github/workflows/update-ci-job-registry.yaml
  • .github/workflows/validate-cpo-overrides.yaml
  • .github/workflows/verify-reusable.yaml
🚧 Files skipped from review as they are similar to previous changes (11)
  • .github/workflows/docs-build-reusable.yaml
  • .github/workflows/gitlint-reusable.yaml
  • .github/workflows/gocacheprog-test-reusable.yaml
  • .github/workflows/validate-cpo-overrides.yaml
  • .github/workflows/codespell-reusable.yaml
  • .github/workflows/cpo-container-sync-reusable.yaml
  • .github/workflows/lint-reusable.yaml
  • .github/workflows/envtest-ocp-reusable.yaml
  • .github/workflows/reusable-claude-on-pr.yaml
  • .github/workflows/test-reusable.yaml
  • .github/workflows/envtest-kube-reusable.yaml

Comment on lines +15 to 17
- uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
with:
token: ${{ secrets.COMMUNITY_FORK_TOKEN }}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🔒 Security & Privacy | 🟠 Major | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

git ls-files .github/workflows/update-ci-job-registry.yaml
wc -l .github/workflows/update-ci-job-registry.yaml
cat -n .github/workflows/update-ci-job-registry.yaml

Repository: openshift/hypershift

Length of output: 2759


🏁 Script executed:

#!/bin/bash
set -euo pipefail

# Show any nearby references to COMMUNITY_FORK_TOKEN, GH_TOKEN, git push, and checkout credential settings.
rg -n -C 3 'COMMUNITY_FORK_TOKEN|GH_TOKEN|persist-credentials|git push|actions/checkout' .github/workflows/update-ci-job-registry.yaml .github/workflows -g '*.yaml'

Repository: openshift/hypershift

Length of output: 19971


Avoid persisting COMMUNITY_FORK_TOKEN from checkout. actions/checkout stores the token in git config by default, and this job runs repository code before the later git push. Set persist-credentials: false here and make the push step authenticate explicitly.

Proposed checkout change
       - uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
         with:
           token: ${{ secrets.COMMUNITY_FORK_TOKEN }}
+          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
- uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
with:
token: ${{ secrets.COMMUNITY_FORK_TOKEN }}
- uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
with:
token: ${{ secrets.COMMUNITY_FORK_TOKEN }}
persist-credentials: false
🧰 Tools
🪛 zizmor (1.26.1)

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

(artipacked)

🤖 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/update-ci-job-registry.yaml around lines 15 - 17, Update
the actions/checkout step in the CI workflow to set persist-credentials to
false, preventing COMMUNITY_FORK_TOKEN from being stored in git configuration.
Then update the later git push step to authenticate explicitly using the
intended token while preserving its existing push behavior.

Sources: Path instructions, Linters/SAST tools

@openshift-ci

openshift-ci Bot commented Aug 21, 2026

Copy link
Copy Markdown
Contributor

Stale PRs are closed after 21d of inactivity.

If this PR is still relevant, comment to refresh it or remove the stale label.
Mark the PR as fresh by commenting /remove-lifecycle stale.

If this PR is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci Bot added lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. labels Aug 21, 2026
@openshift-ci

openshift-ci Bot commented Aug 21, 2026

Copy link
Copy Markdown
Contributor

rebase

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@openshift-ci

openshift-ci Bot commented Sep 4, 2026

Copy link
Copy Markdown
Contributor

Stale PRs rot after 14d of inactivity.

Mark the PR as fresh by commenting /remove-lifecycle rotten.
Rotten PRs close after an additional 7d of inactivity.

If this PR is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci Bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Sep 4, 2026
@openshift-ci

openshift-ci Bot commented Sep 9, 2026

Copy link
Copy Markdown
Contributor

@dependabot[bot]: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/rosa-e2e-images f29ae8c link true /test rosa-e2e-images

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

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

Labels

area/ci-tooling Indicates the PR includes changes for CI or tooling lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. ok-to-test Indicates a non-member PR verified by an org member that is safe to test.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants