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.

@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 from f928afd to aa647bd Compare July 26, 2026 21:22
@renovate
renovate Bot force-pushed the renovate/actions-checkout-7.x branch 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

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