Skip to content

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

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

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

Conversation

@renovate

@renovate renovate Bot commented Jun 22, 2026

Copy link
Copy Markdown

This PR contains the following updates:

Package Type Update Change
actions/checkout action major v6.0.3v7.0.1
actions/checkout action major v5.0.1v7.0.1
actions/checkout action major v4.3.1v7.0.1

Release Notes

actions/checkout (actions/checkout)

v7.0.1

Compare Source

v7.0.0

Compare Source

v7

Compare Source

v6.1.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 these updates again.


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

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

Note

Update actions/checkout to v7.0.1 across all CI workflows

Bumps the pinned actions/checkout action from various older versions (v4–v6) to v7.0.1 (3d3c42e) in all GitHub Actions workflow files, including _checks.yml, lint.yml, public-repo-guard.yml, and release.yml.

Macroscope summarized ea052ed.

@changeset-bot

changeset-bot Bot commented Jun 22, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: c965a72

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@greptile-apps

greptile-apps Bot commented Jun 22, 2026

Copy link
Copy Markdown

PR author is in the excluded authors list.

@wave-bugbot

wave-bugbot Bot commented Jun 25, 2026

Copy link
Copy Markdown

🌊 WAVE BugBot — 12 finding(s)

🔴 10 · 🟠 2

  • 🔴 P0 .github/workflows/_checks.yml:23Unpinned action tag (@v1 vs commit SHA)
    Using a versioned tag (@v1) instead of a specific commit SHA can lead to unexpected behavior if the version is updated.
  • 🔴 P0 .github/workflows/lint.yml:20Unpinned action tag (@v1 vs commit SHA)
    Using a versioned tag (@v1) instead of a specific commit SHA can lead to unexpected behavior if the version is updated.
  • 🔴 P0 .github/workflows/public-repo-guard.yml:45Unpinned action tag (@v1 vs commit SHA)
    Using a versioned tag (@v1) instead of a specific commit SHA can lead to unexpected behavior if the version is updated.
  • 🔴 P0 .github/workflows/publish.yml:14Unpinned action tag (@v1 vs commit SHA)
    Using a versioned tag (@v1) instead of a specific commit SHA can lead to unexpected behavior if the version is updated.
  • 🔴 P0 .github/workflows/_checks.yml:23 CWE-621Unpinned action tag (@v1 vs commit SHA)
    Using a versioned tag (e.g., @v4) for actions can lead to security vulnerabilities if the version is not updated. It's better to use a specific commit SHA to en
  • 🔴 P0 .github/workflows/_checks.yml:54 CWE-621Unpinned action tag (@v1 vs commit SHA)
    Using a versioned tag (e.g., @v4) for actions can lead to security vulnerabilities if the version is not updated. It's better to use a specific commit SHA to en
  • 🔴 P0 .github/workflows/_checks.yml:114 CWE-621Unpinned action tag (@v1 vs commit SHA)
    Using a versioned tag (e.g., @v4) for actions can lead to security vulnerabilities if the version is not updated. It's better to use a specific commit SHA to en
  • 🔴 P0 .github/workflows/lint.yml:20 CWE-621Unpinned action tag (@v1 vs commit SHA)
    Using a versioned tag (e.g., @v6) for actions can lead to security vulnerabilities if the version is not updated. It's better to use a specific commit SHA to en
  • 🔴 P0 .github/workflows/public-repo-guard.yml:45 CWE-621Unpinned action tag (@v1 vs commit SHA)
    Using a versioned tag (e.g., @v5) for actions can lead to security vulnerabilities if the version is not updated. It's better to use a specific commit SHA to en
  • 🔴 P0 .github/workflows/publish.yml:14 CWE-621Unpinned action tag (@v1 vs commit SHA)
    Using a versioned tag (e.g., @v4) for actions can lead to security vulnerabilities if the version is not updated. It's better to use a specific commit SHA to en
  • 🟠 P1 .github/workflows/_checks.yml:23 CWE-426Unpinned search_path in SECURITY DEFINER function
    The search_path is not pinned, which could allow an attacker to shadow your functions by creating objects in earlier schemas.
  • 🟠 P1 .github/workflows/lint.yml:20 CWE-426Unpinned search_path in SECURITY DEFINER function
    The search_path is not pinned, which could allow an attacker to shadow your functions by creating objects in earlier schemas.

severity: critical · major · minor · info — local review · $0 inference · wave-dispatch · react 👍/👎 to tune

@renovate
renovate Bot force-pushed the renovate/actions-checkout-7.x branch 5 times, most recently from e04c834 to 532cff7 Compare July 25, 2026 03:51
@renovate
renovate Bot force-pushed the renovate/actions-checkout-7.x branch from 532cff7 to cfa22aa Compare August 1, 2026 23:12

@devin-ai-integration devin-ai-integration 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.

Devin Review found 3 potential issues.

Open in Devin Review

runs-on: ubuntu-latest
steps:
- uses: actions/checkout@93cb6efe18208431cddfb8368fd83d5badbf9bfd # v5.0.1
- uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🔍 Checkout pin remains without persist-credentials in the guard workflow

This is the only checkout invocation in the repo that omits with: persist-credentials: false, unlike the ones in .github/workflows/lint.yml:20-22 and .github/workflows/_checks.yml:23-25. The SHA bump was applied here, but the hardening convention used elsewhere was not, leaving the token persisted in .git/config while the gitleaks/content-policy scripts run. Pre-existing, but worth aligning while touching the line.

Open in Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.

timeout-minutes: 10
steps:
- uses: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5 # v4.3.1
- uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🔍 Reusable workflow is a mirror copy — bump must also land upstream

The header comment (.github/workflows/_checks.yml:3-6, 47-50) states this file is a mirror of wave-foundation's shared checks.yml/validate-skills.py. Bumping the checkout pin only in this copy risks drift from the upstream source of truth; confirm the same SHA bump is applied there.

Open in Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.

Comment thread .github/workflows/public-repo-guard.yml
@renovate
renovate Bot force-pushed the renovate/actions-checkout-7.x branch from cfa22aa to 487f3ff Compare August 2, 2026 00:34

@devin-ai-integration devin-ai-integration 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.

Devin Review found 1 new potential issue.

Open in Devin Review

timeout-minutes: 10
steps:
- uses: actions/checkout@df4cb1c069e1874edd31b4311f1884172cec0e10 # v6.0.3
- uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🔍 Checkout pin bumped consistently across all workflows

All eight actions/checkout references in .github/workflows/ (_checks.yml:23,54,114, .github/workflows/lint.yml:20, .github/workflows/public-repo-guard.yml:45, .github/workflows/release.yml:44,81,166) now point at the same commit SHA, so the pin-bump transformation was applied completely — no stragglers on the previous v4/v5/v6 SHAs. Worth verifying out-of-band that the SHA 3d3c42e... actually corresponds to the v7.0.1 tag in actions/checkout, since the comment is the only thing asserting that mapping and a wrong comment would mislead future bumps.

Open in Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.

@renovate
renovate Bot force-pushed the renovate/actions-checkout-7.x branch 2 times, most recently from 41bf779 to c965a72 Compare August 2, 2026 04:25
devin-ai-integration[bot]

This comment was marked as resolved.

@renovate
renovate Bot force-pushed the renovate/actions-checkout-7.x branch from c965a72 to ea052ed Compare August 6, 2026 13:48

@devin-ai-integration devin-ai-integration 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.

Devin Review found 1 new potential issue.

Open in Devin Review

runs-on: ubuntu-latest
steps:
- uses: actions/checkout@93cb6efe18208431cddfb8368fd83d5badbf9bfd # v5.0.1
- uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🟨 Checkout in public-repo-guard leaves git credentials on the runner

The checkout step in .github/workflows/public-repo-guard.yml:45 is the only checkout in the repo without persist-credentials: false (all others, e.g. .github/workflows/lint.yml:21-22, set it). The job runs untrusted PR content (a vendored shell script and gitleaks over PR-provided files), so leaving the GITHUB_TOKEN persisted in .git/config widens the blast radius if any step is influenced by PR content.

Open in Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.

@macroscopeapp

macroscopeapp Bot commented Aug 6, 2026

Copy link
Copy Markdown

Approvability

Verdict: Approved ea052ed

Mechanical dependency update bumping actions/checkout from v4/v5/v6 to v7.0.1 across CI workflow files. No behavioral changes to workflows - only SHA pin updates. Review comments are informational suggestions about pre-existing issues, not bugs in this PR.

You can customize Macroscope's approvability policy. Learn more.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants