Skip to content

build(deps): bump the github group across 1 directory with 3 updates - #1313

Open
dependabot[bot] wants to merge 1 commit into
developfrom
dependabot/github_actions/github-fe5e125276
Open

build(deps): bump the github group across 1 directory with 3 updates#1313
dependabot[bot] wants to merge 1 commit into
developfrom
dependabot/github_actions/github-fe5e125276

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 1, 2026

Copy link
Copy Markdown
Contributor

Bumps the github group with 3 updates in the / directory: actions/checkout, actions/setup-node and actions/cache.

Updates actions/checkout from 6.0.2 to 7.0.1

Release notes

Sourced from actions/checkout's releases.

v7.0.1

What's Changed

Full Changelog: actions/checkout@v7...v7.0.1

v7.0.0

What's Changed

New Contributors

Full Changelog: actions/checkout@v6.0.3...v7.0.0

v6.1.0

What's Changed

https://github.blog/changelog/2026-06-18-safer-pull_request_target-defaults-for-github-actions-checkout/ for more details about this breaking change

Full Changelog: actions/checkout@v6.0.3...v6.1.0

v6.0.3

What's Changed

New Contributors

Full Changelog: actions/checkout@v6...v6.0.3

Changelog

Sourced from actions/checkout's changelog.

v7.0.1

v7.0.0

v6.0.3

Commits

Updates actions/setup-node from 6.4.0 to 7.0.0

Release notes

Sourced from actions/setup-node's releases.

v7.0.0

What's Changed

Enhancements:

Bug fixes:

Documentation updates:

Dependency update:

New Contributors

Full Changelog: actions/setup-node@v6...v7.0.0

v6.5.0

What's Changed

Full Changelog: actions/setup-node@v6.4.0...v6.5.0

Commits
  • 8207627 Migrate to ESM and upgrade dependencies (#1574)
  • 04be95c Add cache-primary-key and cache-matched-key as outputs (#1577)
  • 7c2c68d docs: Update caching recommendations to mitigate cache poisoning risks (#1567)
  • 6a61c03 Merge pull request #1569 from jasongin/update-actions-cache-5.1.0
  • 30eb73b Resolve high-severity audit issues
  • 4e1a87a Update dist
  • 360237f Strict equality
  • 4f8aac5 Bump @​actions/cache to 5.1.0, log cache write denied
  • f4a67bb Only use mirrorToken in getManifest if it's provided (#1548)
  • 0355742 Remove dummy NODE_AUTH_TOKEN export (#1558)
  • Additional commits viewable in compare view

Updates actions/cache from 5 to 6

Release notes

Sourced from actions/cache's releases.

v6.0.0

What's Changed

Full Changelog: actions/cache@v5...v6.0.0

v5.1.0

What's Changed

Full Changelog: actions/cache@v5...v5.1.0

v5.0.5

What's Changed

Full Changelog: actions/cache@v5...v5.0.5

v5.0.4

What's Changed

New Contributors

Full Changelog: actions/cache@v5...v5.0.4

v5.0.3

What's Changed

Full Changelog: actions/cache@v5...v5.0.3

v.5.0.2

v5.0.2

What's Changed

... (truncated)

Changelog

Sourced from actions/cache's changelog.

Releases

How to prepare a release

[!NOTE] Relevant for maintainers with write access only.

  1. Switch to a new branch from main.
  2. Run npm test to ensure all tests are passing.
  3. Update the version in https://github.com/actions/cache/blob/main/package.json.
  4. Run npm run build to update the compiled files.
  5. Update this https://github.com/actions/cache/blob/main/RELEASES.md with the new version and changes in the ## Changelog section.
  6. Run licensed cache to update the license report.
  7. Run licensed status and resolve any warnings by updating the https://github.com/actions/cache/blob/main/.licensed.yml file with the exceptions.
  8. Commit your changes and push your branch upstream.
  9. Open a pull request against main and get it reviewed and merged.
  10. Draft a new release https://github.com/actions/cache/releases use the same version number used in package.json
    1. Create a new tag with the version number.
    2. Auto generate release notes and update them to match the changes you made in RELEASES.md.
    3. Toggle the set as the latest release option.
    4. Publish the release.
  11. Navigate to https://github.com/actions/cache/actions/workflows/release-new-action-version.yml
    1. There should be a workflow run queued with the same version number.
    2. Approve the run to publish the new version and update the major tags for this action.

Changelog

6.1.0

6.0.0

  • Updated @actions/cache to ^6.0.1, @actions/core to ^3.0.1, @actions/exec to ^3.0.0, @actions/io to ^3.0.2
  • Migrated to ESM module system
  • Upgraded Jest to v30 and test infrastructure to be ESM compatible

5.0.4

  • Bump minimatch to v3.1.5 (fixes ReDoS via globstar patterns)
  • Bump undici to v6.24.1 (WebSocket decompression bomb protection, header validation fixes)
  • Bump fast-xml-parser to v5.5.6

5.0.3

5.0.2

... (truncated)

Commits
  • 55cc834 Merge pull request #1768 from jasongin/readonly-cache
  • d8cd72f Bump @​actions/cache to v6.1.0 - handle cache write error due to RO token
  • 2c8a9bd Merge pull request #1760 from actions/samirat/esm_migration_and_package_update
  • e9b91fd Prettier fixes
  • e4884b8 Rebuild dist
  • 10baf01 Fixed licenses
  • e39b386 Fix test mock return order
  • b692820 PR feedback
  • 6074912 Rebuild dist bundles as ESM to match type:module
  • 5a912e8 Fix lint and jest issues
  • Additional commits viewable in compare view

Dependabot 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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will 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 version will 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

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>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Aug 1, 2026
@rtibblesbot

rtibblesbot commented Aug 1, 2026

Copy link
Copy Markdown
Contributor

🔵 Review posted

Last updated: 2026-08-01 16:38 UTC

@rtibblesbot rtibblesbot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

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/checkout v7.0.0 (#2454) — "Block checking out fork PR for pull_request_target and workflow_run". src/unsafe-pr-checkout-helper.ts throws when the event is pull_request_target/workflow_run, the PR head repo differs from the base repo, and the resolved ref is the PR head SHA — unless allow-unsafe-pr-checkout: true. visual_tests.yml matches 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-node v7.0.0: ESM migration, node24 runtime, and it no longer exports a dummy NODE_AUTH_TOKEN when none is provided (#1558). npm-publish.yml uses OIDC trusted publishing with no NODE_AUTH_TOKEN, so this should be neutral-to-positive, but it's on: release and can't be validated pre-merge — worth watching the next publish run.
  • actions/cache v6: 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:17nitpick: checkout/setup-node are pinned to exact patch tags while cache floats on @v6. Pre-existing style that dependabot preserved, but worth settling on one convention — and SHA pinning for the pull_request_target workflows, 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

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

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: true

See 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

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

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.1

This is the pattern update_changelog.yml already uses.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant