Skip to content

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

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

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

Conversation

@renovate

@renovate renovate Bot commented Jun 21, 2026

Copy link
Copy Markdown

This PR contains the following updates:

Package Type Update Change
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

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


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 becomes conflicted, 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 Jun 21, 2026

Copy link
Copy Markdown

PR author is in the excluded authors list.

@changeset-bot

changeset-bot Bot commented Jun 21, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: ab37f63

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 4 times, most recently from c7fb4b3 to 1a4654e Compare July 27, 2026 01:37
@renovate
renovate Bot force-pushed the renovate/actions-checkout-7.x branch from 1a4654e to ab37f63 Compare July 31, 2026 21:23
@renovate
renovate Bot force-pushed the renovate/actions-checkout-7.x branch from ab37f63 to 64a2016 Compare August 11, 2026 16:35

@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

@devin-ai-integration devin-ai-integration Bot Aug 11, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🔍 Verify the pinned SHA actually corresponds to the v7.0.1 tag

All seven actions/checkout pins were updated consistently to 3d3c42e5aac5ba805825da76410c181273ba90b1 with a # v7.0.1 comment, so the mechanical transformation is complete (.github/workflows/_checks.yml:23,54,114, .github/workflows/foundation-gate.yml:44,71,95, .github/workflows/public-repo-guard.yml:45). The comment is the only human-readable link between the SHA and the release; since a wrong comment silently defeats the whole pinning discipline, it is worth confirming the SHA resolves to the v7.0.1 tag in actions/checkout (e.g. gh api repos/actions/checkout/git/ref/tags/v7.0.1) before merging. Note that public-repo-guard was previously pinned to a v5 SHA while the other files were on v4.3.1, so this is a multi-major jump for every workflow at once.

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 wave-foundation; pin bump may drift

.github/workflows/_checks.yml:3-6 and .github/workflows/foundation-gate.yml:1-10 state this file is an inlined copy of wave-foundation/.github/workflows/checks.yml that must be kept in sync. Bumping the checkout pin only here introduces drift from the upstream source of truth unless the same bump lands there too.

Open in Devin Review

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

Comment thread .github/workflows/public-repo-guard.yml
@macroscopeapp

macroscopeapp Bot commented Aug 11, 2026

Copy link
Copy Markdown

Approvability

Verdict: Needs human review

All changed workflow files are owned by wave-av/core-team, not the renovate bot. Additionally, an unresolved review comment raises a security concern about persist-credentials configuration in the public-repo-guard workflow. Code owners should review this multi-major version bump.

No code changes detected at c02417d. Prior analysis still applies.

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

@renovate
renovate Bot force-pushed the renovate/actions-checkout-7.x branch from 64a2016 to 310b24a Compare August 11, 2026 23:01
devin-ai-integration[bot]

This comment was marked as resolved.

@renovate
renovate Bot force-pushed the renovate/actions-checkout-7.x branch 2 times, most recently from 310b24a to 8ddaaca Compare August 14, 2026 16:42
@renovate
renovate Bot force-pushed the renovate/actions-checkout-7.x branch from 8ddaaca to c02417d Compare August 26, 2026 18:10
@codeant-ai

codeant-ai Bot commented Aug 26, 2026

Copy link
Copy Markdown

Your free trial PR review limit of 300 PRs has been reached. Please upgrade your plan to continue using CodeAnt AI.

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