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

[renovate]

This PR contains the following updates:

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

---

Release Notes

actions/checkout (actions/checkout)

v7.0.1

Compare Source

• Bump github/codeql-action from 3 to 4 by @​dependabot[bot] in #​2475
• Bump actions/setup-node from 4 to 6 by @​dependabot[bot] in #​2477
• Bump docker/build-push-action from 6.5.0 to 7.2.0 by @​dependabot[bot] in #​2478
• Bump docker/login-action from 3.3.0 to 4.2.0 by @​dependabot[bot] in #​2479
• Bump actions/checkout from 6 to 7 by @​dependabot[bot] in #​2488
• Bump actions/upload-artifact from 4 to 7 by @​dependabot[bot] in #​2476
• eslint 9 by @​dependabot[bot] in #​2474
• Bump the minor-actions-dependencies group with 2 updates by @​dependabot[bot] in #​2499
• skip running unsafe pr check if input is default by @​aiqiaoy in #​2518
• trim only ascii whitespace for branch by @​aiqiaoy in #​2521
• escape values passed to --unset by @​aiqiaoy in #​2530

v7.0.0

Compare Source

• Block checking out fork PR for pull_request_target and workflow_run by @​aiqiaoy in #​2454
• Bump actions/publish-immutable-action from 0.0.3 to 0.0.4 in the minor-actions-dependencies group across 1 directory by @​dependabot[bot] in #​2458
• Bump flatted from 3.3.1 to 3.4.2 by @​dependabot[bot] in #​2460
• Bump js-yaml from 4.1.0 to 4.2.0 by @​dependabot[bot] in #​2461
• Bump @​actions/core and @​actions/tool-cache and Remove uuid by @​dependabot[bot] in #​2459
• upgrade module to esm and update dependencies by @​aiqiaoy in #​2463
• Bump the minor-npm-dependencies group across 1 directory with 3 updates by @​dependabot[bot] in #​2462

v7

Compare Source

• Block checking out fork PR for pull_request_target and workflow_run by @​aiqiaoy in #​2454
• Bump actions/publish-immutable-action from 0.0.3 to 0.0.4 in the minor-actions-dependencies group across 1 directory by @​dependabot[bot] in #​2458
• Bump flatted from 3.3.1 to 3.4.2 by @​dependabot[bot] in #​2460
• Bump js-yaml from 4.1.0 to 4.2.0 by @​dependabot[bot] in #​2461
• Bump @​actions/core and @​actions/tool-cache and Remove uuid by @​dependabot[bot] in #​2459
• upgrade module to esm and update dependencies by @​aiqiaoy in #​2463
• Bump the minor-npm-dependencies group across 1 directory with 3 updates by @​dependabot[bot] in #​2462

v6.1.0

Compare Source

v6.0.3

Compare Source

• Fix checkout init for SHA-256 repositories by @​yaananth in #​2439
• fix: expand merge commit SHA regex and add SHA-256 test cases by @​yaananth in #​2414

v6.0.2

Compare Source

• Fix tag handling: preserve annotations and explicit fetch-tags by @​ericsciple in #​2356

v6.0.1

Compare Source

• Add worktree support for persist-credentials includeIf by @​ericsciple in #​2327

v6.0.0

Compare Source

• Persist creds to a separate file by @​ericsciple in #​2286
• Update README to include Node.js 24 support details and requirements by @​salmanmkc in #​2248

v6

Compare Source

• Fix checkout init for SHA-256 repositories by @​yaananth in #​2439
• fix: expand merge commit SHA regex and add SHA-256 test cases by @​yaananth in #​2414

v5.1.0

Compare Source

v5.0.1

Compare Source

• Port v6 cleanup to v5 by @​ericsciple in #​2301

v5.0.0

Compare Source

• Update actions checkout to use node 24 by @​salmanmkc in #​2226

v5

Compare Source

• Port v6 cleanup to v5 by @​ericsciple in #​2301

---

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.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 532cff7

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]

PR author is in the excluded authors list.

[wave-bugbot]

🌊 WAVE BugBot — 12 finding(s)

🔴 10 · 🟠 2

• 🔴 P0 .github/workflows/_checks.yml:23 — Unpinned 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:20 — Unpinned 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:45 — Unpinned 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:14 — Unpinned 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-621 — Unpinned 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-621 — Unpinned 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-621 — Unpinned 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-621 — Unpinned 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-621 — Unpinned 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-621 — Unpinned 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-426 — Unpinned 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-426 — Unpinned 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}