Skip to content

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

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

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

Conversation

@renovate

@renovate renovate Bot commented Jul 3, 2026

Copy link
Copy Markdown

This PR contains the following updates:

Package Type Update Change
actions/checkout action major v4v7
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

v6.0.3

Compare Source

v6.0.2

Compare Source

v6.0.1

Compare Source

v6.0.0

Compare Source

v6

Compare Source

v5.1.0

Compare Source

v5.0.1

Compare Source

v5.0.0

Compare Source

v5

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.


Open in Devin Review

@greptile-apps

greptile-apps Bot commented Jul 3, 2026

Copy link
Copy Markdown

PR author is in the excluded authors list.

@changeset-bot

changeset-bot Bot commented Jul 3, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 53d9d4c

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

@renovate
renovate Bot force-pushed the renovate/actions-checkout-7.x branch 5 times, most recently from a6af343 to f928afd Compare July 22, 2026 05:14
@renovate
renovate Bot force-pushed the renovate/actions-checkout-7.x branch 2 times, most recently from aa647bd to 53d9d4c Compare August 1, 2026 03:53
@wave-bugbot

wave-bugbot Bot commented Aug 12, 2026

Copy link
Copy Markdown

🌊 WAVE BugBot — 5 finding(s)

🔴 3 · 🟠 2

  • 🔴 P0 .github/workflows/_checks.yml:23 CWE-862Unpinned action tag (@v1)
    The action tag is pinned to a specific commit SHA, which can lead to security vulnerabilities if the commit is later changed or removed.
  • 🔴 P0 .github/workflows/_checks.yml:114 CWE-89Potential SQL injection vulnerability due to lack of parameterization
    The code appears to use a raw string for a command or query, which could be vulnerable to SQL injection if user input is involved.
  • 🔴 P0 .github/workflows/_checks.yml:114 CWE-78Potential shell injection vulnerability due to lack of parameterization
    The code appears to use a raw string for a command or query, which could be vulnerable to shell injection if user input is involved.
  • 🟠 P1 .github/workflows/_checks.yml:23 CWE-426Unpinned search_path in SECURITY DEFINER function
    The action tag is pinned to a specific commit SHA (v7.0.1), but the search_path is not explicitly set or pinned, which could allow an attacker to shadow functio
  • 🟠 P1 .github/workflows/_checks.yml:23 CWE-426Unpinned search_path (must end pg_temp)
    The search_path is not pinned, which can lead to security vulnerabilities if an attacker can create objects in an earlier schema and shadow yours.

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 from 53d9d4c to 7b6be07 Compare August 14, 2026 17:26

@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 4 potential issues.

Open in Devin Review

working-directory: sdk-typescript
steps:
- 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.

🔍 Mixed pinning styles for the same action version across workflows

The repo pins actions/checkout two different ways: by commit SHA with a version comment in .github/workflows/_checks.yml:23,54,114 and .github/workflows/public-repo-guard.yml:45, but by floating major tag (@v7) in the ten publish/test/release workflows (e.g. .github/workflows/publish-npm.yml:30, .github/workflows/test-go.yml:31). The bump keeps that inconsistency. Both SHA sites now use the same commit (3d3c42e…) with the same # v7.0.1 comment, so they are internally consistent, but the tag-pinned workflows — including the ones with publish privileges and id-token: write — remain mutable references. Worth deciding on one convention, especially for the release lanes.

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.

🔍 _checks.yml is documented as a mirror of a shared upstream workflow

The header of this file states it is the reusable cross-project gate that other WAVE repos consume via wave-av/wave-foundation/.github/workflows/checks.yml@master and that it must stay in sync with wave-foundation/scripts/validate-skills.py. Bumping the checkout pin only here introduces drift from the upstream copy; the same bump should be landed in wave-foundation (or this file re-synced) so consumers don't diverge.

Open in Devin Review

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

working-directory: sdk-typescript
steps:
- 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.

🟨 Most workflows pin actions/checkout to a mutable tag instead of a commit SHA

The bump moves actions/checkout to @v7 in the publish/test workflows (e.g. .github/workflows/publish-npm.yml:30, .github/workflows/publish-crates.yml:31,51, .github/workflows/publish-rubygems.yml:28,49, .github/workflows/publish-pypi.yml:28, .github/workflows/release-go.yml:22, .github/workflows/registry-parity.yml:27, .github/workflows/test-*.yml), while the security gates in .github/workflows/_checks.yml and .github/workflows/public-repo-guard.yml use a full commit SHA. A floating major tag is mutable, so a compromised or force-moved tag would execute attacker-controlled code in workflows that hold OIDC trusted-publishing rights (id-token: write) and can publish packages to npm/crates.io/RubyGems/PyPI.

Open in Devin Review

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

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.

🟨 Security gate checkout keeps git credentials available to later steps

The checkout step in the public-repo-guard security gate (.github/workflows/public-repo-guard.yml:45) does not set persist-credentials: false, unlike every other checkout in the repo (e.g. .github/workflows/_checks.yml:24-25). The workflow then downloads and executes an external binary (gitleaks) and runs a repo-local shell script in the same job, both of which can read the persisted GITHUB_TOKEN from .git/config.

Open in Devin Review

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

@macroscopeapp

macroscopeapp Bot commented Aug 14, 2026

Copy link
Copy Markdown

Approvability

Verdict: Needs human review

Updates actions/checkout from v4 to v7 across 12 workflow files. While this is a standard dependency update, all modified files are owned by wave-av/sdk-owners and should be reviewed by the designated code owners.

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