Skip to content

build(deps): bump actions/cache from 5.0.3 to 6.1.0 - #4359

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/actions/cache-6.1.0
Open

build(deps): bump actions/cache from 5.0.3 to 6.1.0#4359
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/actions/cache-6.1.0

Conversation

@dependabot

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

Copy link
Copy Markdown
Contributor

Bumps actions/cache from 5.0.3 to 6.1.0.

Release notes

Sourced from actions/cache's releases.

v6.1.0

What's Changed

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

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

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 dependabot Bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update Github_actions code labels Sep 1, 2026
@dependabot
dependabot Bot requested a review from a team as a code owner September 1, 2026 22:42
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update Github_actions code labels Sep 1, 2026
Bumps [actions/cache](https://github.com/actions/cache) from 5.0.3 to 6.1.0.
- [Release notes](https://github.com/actions/cache/releases)
- [Changelog](https://github.com/actions/cache/blob/main/RELEASES.md)
- [Commits](actions/cache@cdf6c1f...55cc834)

---
updated-dependencies:
- dependency-name: actions/cache
  dependency-version: 6.1.0
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/github_actions/actions/cache-6.1.0 branch from 5b233b8 to 081c75c Compare September 10, 2026 20:39

@claude claude Bot 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.

Looks good, straightforward dependency bump.

What was reviewed: the single-line change to .github/workflows/ci.yml bumping the pinned commit SHA (and version comment) for actions/cache from v5.0.3 to v6.1.0 in the "Cache ESLint" step. The action is still pinned to a full commit SHA (not a mutable tag), and the cache path/key inputs are unchanged.

Extended reasoning...

Overview

The PR is a Dependabot-generated bump of the actions/cache GitHub Action used in the "Cache ESLint" step of .github/workflows/ci.yml, moving the pinned commit SHA from v5.0.3 (cdf6c1fa...) to v6.1.0 (55cc8345...), with the version comment updated to match. No other lines (cache path, cache key expression, job structure) were touched.

Security risks

None of concern. The action remains pinned to a full commit SHA rather than a mutable tag, which is the recommended supply-chain-safe pattern, so this bump does not introduce any new trust exposure beyond what already existed. The upstream release notes describe internal packaging/ESM migration changes and a fix for read-only cache token handling — nothing that changes the semantics of this workflow's cache step in a way that would be security relevant here.

Level of scrutiny

This warrants only a light review: it's a one-line, mechanical version/SHA bump in a CI config file, isolated to a non-critical caching step (ESLint cache), authored by Dependabot following its standard process. No application code, secrets, permissions, or auth logic is touched.

Other factors

No CODEOWNERS/ANTOWNERS restrictions apply, no CLAUDE.md conventions exist for this path, and the bug hunting system reported zero findings. The diff is fully self-contained and verified directly above.

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.

0 participants