Skip to content

chore(deps): update actions/checkout action to v7 - #215

Open
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/actions-checkout-7.x
Open

chore(deps): update actions/checkout action to v7#215
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/actions-checkout-7.x

Conversation

@renovate

@renovate renovate Bot commented Jul 11, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
actions/checkout action major v4v7

Release Notes

actions/checkout (actions/checkout)

v7.0.1

Compare Source

v7.0.0

Compare Source

v6.1.0

Compare Source

v6.0.3

Compare Source

v6.0.2

Compare Source

v6.0.1

Compare Source

v6.0.0

Compare Source

v5.1.0

Compare Source

v5.0.1

Compare Source

v5.0.0

Compare Source


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Jul 11, 2026

Copy link
Copy Markdown

Deploying dev-blog with  Cloudflare Pages  Cloudflare Pages

Latest commit: cf78a63
Status: ✅  Deploy successful!
Preview URL: https://216b196e.dev-blog-10f.pages.dev
Branch Preview URL: https://renovate-actions-checkout-7.dev-blog-10f.pages.dev

View logs

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Reviewed actions/checkout v4 → v7 in .github/workflows/visual.yml against the v5, v6, and v7 breaking changes. No workflow mitigation is required, and this PR should not add allow-unsafe-pr-checkout.

This is the only checkout in the repo. The Visual job uses a default checkout (no custom ref, repository, or token) on push to master and pull_request, running on GitHub-hosted ubuntu-latest.

Version Breaking change Applies here?
v5 Action runtime is Node 24; needs Actions Runner ≥ v2.327.1 No. GitHub-hosted runners already meet this. CI on this PR used runner 2.335.1.
v6 persist-credentials writes to $RUNNER_TEMP instead of .git/config. Docker container actions need runner ≥ v2.329.0. Git commands on the job still work without workflow edits. No. No container actions, no later authenticated git steps.
v7 Refuses to check out fork PR code on pull_request_target / workflow_run unless allow-unsafe-pr-checkout: true. No. This workflow does not use those triggers, so the new default is a no-op. Leave the flag unset.

v7 also migrates the action to ESM and bumps internal dependencies. That is an implementation change, not a consumer API change.

CI evidence: Visual snapshot tests succeeded with actions/checkout@v7 (resolved to 9c091bb). Logs show a normal pull_request merge-ref checkout with allow-unsafe-pr-checkout: false.

No follow-up commits are needed for this bump.

Open in Web View Automation 

Sent by Cursor Automation: Dep review

steps:
- name: Checkout
uses: actions/checkout@v4
uses: actions/checkout@v7

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Default actions/checkout@v7 is compatible with this job. The v7 fork-PR guard only fires on pull_request_target / workflow_run; this workflow uses push + pull_request, so do not add allow-unsafe-pr-checkout.

v5 (Node 24 runtime) and v6 (credentials under $RUNNER_TEMP) also do not require workflow changes here: GitHub-hosted ubuntu-latest, no Docker container actions, no later authenticated git steps. CI already passed with this pin.

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant