Skip to content

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

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

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

Conversation

@renovate

@renovate renovate Bot commented Jul 18, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
actions/checkout action major v5v7

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


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • "every weekend"
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

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 this update again.


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

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

@renovate

renovate Bot commented Jul 18, 2026

Copy link
Copy Markdown
Contributor Author

Branch automerge failure

This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.


  • Branch has one or more failed status checks

@vercel

vercel Bot commented Jul 18, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
pgtyped Error Error Jul 18, 2026 5:01am

emmanuel added a commit to pelotech/pgtyped that referenced this pull request Sep 10, 2026
Adopts upstream PR adelsz#642 across all three workflows, and takes the pnpm action
with it. Both are pure runtime bumps for a consumer: `action.yml` for
checkout v5 and v7 declares an identical set of inputs and outputs, and
pnpm/action-setup v4 and v6 likewise, differing only in `using: node20` →
`node24`. checkout v6 moved the token out of `.git/config` into a separate
credential file, and v7 refuses to check out a fork's head for
`pull_request_target` and `workflow_run`; nothing here reads git credentials or
uses either trigger.

Two actions are deliberately left behind, because both majors change behaviour
rather than just the runtime:

- `actions/setup-node@v4` is three majors behind. v5 caches automatically when
  `package.json` has a `packageManager` field — which this repo has — and v6
  then narrowed that to npm only. Every workflow here already passes
  `cache: 'pnpm'`, so the interaction needs to be worked out rather than
  assumed.
- `googleapis/release-please-action@v4` is one major behind. v5 is a node24
  bump, but it carries release-please 17.3.0 → 17.6.0 with it, and this is the
  one workflow whose first real run is on master.
emmanuel added a commit to pelotech/pgtyped that referenced this pull request Sep 10, 2026
adelsz#580, adelsz#624 and adelsz#642 move out of "Worth adopting from upstream" into "Fixed on
this branch", keeping their reproductions and gaining what was actually done.
Three things each entry now records that the original did not: for adelsz#580, that
upstream's constructor-argument mechanism was rejected in favour of reading the
name off the IR, and the tag limit found while doing it — an unnamed tag reports
the placeholder `queryName` of `'query'`, because codegen derives a tag's name
at generation time and it never reaches the emitted query; for adelsz#624, that pg18
was re-verified on the current tree rather than trusted from the first pass, and
that the CI matrix the entry wanted is a workflow change rather than an image
tag; for adelsz#642, why `actions/setup-node` and `googleapis/release-please-action`
are left behind while `pnpm/action-setup` was bumped alongside checkout.

Cross-references follow: adelsz#522 leaves "Unimplemented feature requests", the
"Not applicable" note on adelsz#580's mechanism points at what replaced it, the
adelsz#624 line in "What was not verified" says the gap survived a second run, and
the index marks all four numbers.
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