build(deps): bump the github group across 1 directory with 3 updates - #1313
build(deps): bump the github group across 1 directory with 3 updates#1313dependabot[bot] wants to merge 1 commit into
Conversation
Bumps the github group with 3 updates in the / directory: [actions/checkout](https://github.com/actions/checkout), [actions/setup-node](https://github.com/actions/setup-node) and [actions/cache](https://github.com/actions/cache). Updates `actions/checkout` from 6.0.2 to 7.0.1 - [Release notes](https://github.com/actions/checkout/releases) - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md) - [Commits](actions/checkout@v6.0.2...v7.0.1) Updates `actions/setup-node` from 6.4.0 to 7.0.0 - [Release notes](https://github.com/actions/setup-node/releases) - [Commits](actions/setup-node@v6.4.0...v7.0.0) Updates `actions/cache` from 5 to 6 - [Release notes](https://github.com/actions/cache/releases) - [Changelog](https://github.com/actions/cache/blob/main/RELEASES.md) - [Commits](actions/cache@v5...v6) --- updated-dependencies: - dependency-name: actions/checkout dependency-version: 7.0.1 dependency-type: direct:production update-type: version-update:semver-major dependency-group: github - dependency-name: actions/setup-node dependency-version: 7.0.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: github - dependency-name: actions/cache dependency-version: '6' dependency-type: direct:production update-type: version-update:semver-major dependency-group: github ... Signed-off-by: dependabot[bot] <support@github.com>
🔵 Review postedLast updated: 2026-08-01 16:38 UTC |
rtibblesbot
left a comment
There was a problem hiding this comment.
PR #1313 — grouped GitHub Actions bump, three major jumps in CI-only (development) dependencies. CI is green, but it only exercises lint.yml.
| Action | From → To | Semver |
|---|---|---|
actions/checkout |
6.0.2 → 7.0.1 | major |
actions/setup-node |
6.4.0 → 7.0.0 | major |
actions/cache |
5 → 6 | major |
Breaking changes
actions/checkoutv7.0.0 (#2454) — "Block checking out fork PR forpull_request_targetandworkflow_run".src/unsafe-pr-checkout-helper.tsthrows when the event ispull_request_target/workflow_run, the PR head repo differs from the base repo, and the resolvedrefis the PR head SHA — unlessallow-unsafe-pr-checkout: true.visual_tests.ymlmatches all three conditions on both its checkout-from-PR steps, so Percy visual tests will fail on every fork PR (i.e. essentially every contributor PR in this repo) once this merges. Requires a code change alongside the bump — see the two inline comments.actions/setup-nodev7.0.0: ESM migration, node24 runtime, and it no longer exports a dummyNODE_AUTH_TOKENwhen none is provided (#1558).npm-publish.ymluses OIDC trusted publishing with noNODE_AUTH_TOKEN, so this should be neutral-to-positive, but it'son: releaseand can't be validated pre-merge — worth watching the next publish run.actions/cachev6: ESM migration,@actions/cache^6.0.1, node24 runtime. No input/output changes.
Security fixes / peer deps: none. The checkout change is a hardening measure, not a CVE fix.
CI: passing, but only for lint.yml. visual_tests.yml and update_changelog.yml are pull_request_target workflows, so GitHub ran the base branch copies — this PR's edits to them never executed. Frontend tests and Frontend Visual Tests both reported skipping (path filters). npm-publish.yml, update_project_items_on_release.yml and sync_kds_roadmap_statuses.yml don't run on PRs at all. Treat green CI as evidence for lint.yml only.
Comments on lines not in diff
- .github/workflows/lint.yml:17 — nitpick:
checkout/setup-nodeare pinned to exact patch tags whilecachefloats on@v6. Pre-existing style that dependabot preserved, but worth settling on one convention — and SHA pinning for thepull_request_targetworkflows, which hold repository secrets.
update_changelog.yml is already safe: ref: ${{ github.event.pull_request.base.ref }} plus persist-credentials: false means it never touches fork code and needs no opt-in.
@rtibblesbot's comments are generated by an LLM, and should be evaluated accordingly
How was this generated?
Ran a dependency-update review pipeline over the version bump:
- Classified the bump by semver (patch / minor / major) and dependency type (production vs. development)
- Extracted the changelog and release notes across the version range
- Assessed compatibility with this project's usage and whether any code changes are required
- Treated CI as the primary safety net
- Scaled the review depth to the update's risk
- Chose the verdict from semver risk, changelog findings, and CI status
| - name: Checkout code from PR | ||
| if: github.event.pull_request.merged == false | ||
| uses: actions/checkout@v6.0.2 | ||
| uses: actions/checkout@v7.0.1 |
There was a problem hiding this comment.
blocking: checkout v7 refuses this checkout. Event is pull_request_target (line 4), ref is the fork PR head SHA (line 47), and contributors work from forks — all three guard conditions in src/unsafe-pr-checkout-helper.ts hold, so the step throws and Percy never runs.
The existing mitigation for the pwn-request risk here is environment: percy_tests (lines 32–39) gating PERCY_TOKEN. If that's considered sufficient, opt back in explicitly:
with:
ref: ${{ github.event.pull_request.head.sha }}
allow-unsafe-pr-checkout: trueSee gh.io/securely-using-pull_request_target — the flag is a deliberate acknowledgement, so confirm the percy_tests environment has required reviewers configured first.
(The "Checkout code from target branch" step below is fine — base.ref is a branch name, so the guard returns early.)
| steps: | ||
| - name: Checkout code from PR | ||
| uses: actions/checkout@v6.0.2 | ||
| uses: actions/checkout@v7.0.1 |
There was a problem hiding this comment.
blocking: Same v7 guard failure, and this one is the riskier of the two — no environment gate, and it runs github-script with secrets.GITHUB_TOKEN.
This job only needs ./.github/githubUtils.js (lines 103, 110); it never uses PR content. Drop the ref: so it checks out the base repo — isDefaultCheckout short-circuits before the assertion, and no opt-in flag is needed:
- name: Checkout base repo for helper scripts
uses: actions/checkout@v7.0.1This is the pattern update_changelog.yml already uses.
Bumps the github group with 3 updates in the / directory: actions/checkout, actions/setup-node and actions/cache.
Updates
actions/checkoutfrom 6.0.2 to 7.0.1Release notes
Sourced from actions/checkout's releases.
Changelog
Sourced from actions/checkout's changelog.
Commits
3d3c42eprep v7.0.1 release (#2531)2880268escape values passed to --unset (#2530)12cd223trim only ascii whitespace for branch (#2521)62661c4skip running unsafe pr check if input is default (#2518)e8d4307Bump the minor-actions-dependencies group with 2 updates (#2499)631c942eslint 9 (#2474)4f1f4aeBump actions/upload-artifact from 4 to 7 (#2476)ba09753Bump actions/checkout from 6 to 7 (#2488)b9e0990Bump docker/login-action from 3.3.0 to 4.2.0 (#2479)e8cb398Bump docker/build-push-action from 6.5.0 to 7.2.0 (#2478)Updates
actions/setup-nodefrom 6.4.0 to 7.0.0Release notes
Sourced from actions/setup-node's releases.
Commits
8207627Migrate to ESM and upgrade dependencies (#1574)04be95cAdd cache-primary-key and cache-matched-key as outputs (#1577)7c2c68ddocs: Update caching recommendations to mitigate cache poisoning risks (#1567)6a61c03Merge pull request #1569 from jasongin/update-actions-cache-5.1.030eb73bResolve high-severity audit issues4e1a87aUpdate dist360237fStrict equality4f8aac5Bump@actions/cacheto 5.1.0, log cache write deniedf4a67bbOnly usemirrorTokeningetManifestif it's provided (#1548)0355742Remove dummy NODE_AUTH_TOKEN export (#1558)Updates
actions/cachefrom 5 to 6Release notes
Sourced from actions/cache's releases.
... (truncated)
Changelog
Sourced from actions/cache's changelog.
... (truncated)
Commits
55cc834Merge pull request #1768 from jasongin/readonly-cached8cd72fBump@actions/cacheto v6.1.0 - handle cache write error due to RO token2c8a9bdMerge pull request #1760 from actions/samirat/esm_migration_and_package_updatee9b91fdPrettier fixese4884b8Rebuild dist10baf01Fixed licensese39b386Fix test mock return orderb692820PR feedback6074912Rebuild dist bundles as ESM to match type:module5a912e8Fix lint and jest issuesDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions