Skip to content

chore(deps): bump actions/cache from 5.0.5 to 6.1.0#319

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

chore(deps): bump actions/cache from 5.0.5 to 6.1.0#319
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 Jul 1, 2026

Copy link
Copy Markdown
Contributor

Bumps actions/cache from 5.0.5 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

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 compatibility score

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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Summary by cubic

Update CI to use actions/cache v6.1.0 for better handling of read-only tokens and the latest internal updates. No workflow changes required.

  • Dependencies
    • Bumped actions/cache from 5.0.5 to 6.1.0 in .github/workflows/ci.yml.

Written for commit ef0b9d4. Summary will update on new commits.

Bumps [actions/cache](https://github.com/actions/cache) from 5.0.5 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@27d5ce7...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 added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Jul 1, 2026
@greptile-apps

greptile-apps Bot commented Jul 1, 2026

Copy link
Copy Markdown

Greptile Summary

This is a Dependabot-generated bump of actions/cache from v5.0.5 to v6.1.0 in the CI workflow. The new SHA corresponds to v6.1.0, which migrates to ESM and adds graceful handling of cache write errors when using a read-only token.

  • The pinned SHA on line 112 was updated correctly, but the inline comment # v5 was not updated to # v6.1.0, leaving it misleading.
  • The v6.0.0 release is a major-version change (ESM migration); no changes to with: inputs or outputs were needed for this usage.

Confidence Score: 4/5

Safe to merge — this is a straightforward SHA pin update to a well-known GitHub-maintained action with no interface changes required.

The only issue is a stale inline comment (# v5) that was not updated to match the new SHA, which now resolves to v6.1.0. The workflow inputs and outputs are unchanged and remain compatible with the new major version.

.github/workflows/ci.yml line 112 — the inline version comment needs updating from # v5 to # v6.1.0.

Important Files Changed

Filename Overview
.github/workflows/ci.yml Bumps the pinned SHA for actions/cache from v5.0.5 to v6.1.0; the version comment was not updated alongside the SHA.

Sequence Diagram

%%{init: {'theme': 'neutral'}}%%
sequenceDiagram
    participant Runner as GitHub Actions Runner
    participant Cache as actions/cache@v6.1.0
    participant Store as GitHub Cache Store

    Runner->>Cache: Restore cache (key: git-folder)
    Cache->>Store: Lookup cache entry
    Store-->>Cache: Cache hit / miss
    Cache-->>Runner: Restore result

    Note over Runner: ... job steps execute ...

    Runner->>Cache: Save cache (post step)
    Cache->>Store: Upload cache (write token required)
    alt Read-only token (new in v6.1.0)
        Store-->>Cache: Write error (403)
        Cache-->>Runner: Log debug warning (no failure)
    else Normal token
        Store-->>Cache: Cache saved
        Cache-->>Runner: Success
    end
Loading
%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
sequenceDiagram
    participant Runner as GitHub Actions Runner
    participant Cache as actions/cache@v6.1.0
    participant Store as GitHub Cache Store

    Runner->>Cache: Restore cache (key: git-folder)
    Cache->>Store: Lookup cache entry
    Store-->>Cache: Cache hit / miss
    Cache-->>Runner: Restore result

    Note over Runner: ... job steps execute ...

    Runner->>Cache: Save cache (post step)
    Cache->>Store: Upload cache (write token required)
    alt Read-only token (new in v6.1.0)
        Store-->>Cache: Write error (403)
        Cache-->>Runner: Log debug warning (no failure)
    else Normal token
        Store-->>Cache: Cache saved
        Cache-->>Runner: Success
    end
Loading

Fix All in Claude Code

Prompt To Fix All With AI
Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 1
.github/workflows/ci.yml:112
The pinned SHA now resolves to `v6.1.0` (a major version bump), but the inline comment was not updated from `# v5`. This makes the comment misleading for anyone checking which version is actually pinned.

```suggestion
        uses: actions/cache@55cc8345863c7cc4c66a329aec7e433d2d1c52a9 # v6.1.0
```

Reviews (1): Last reviewed commit: "chore(deps): bump actions/cache from 5.0..." | Re-trigger Greptile

Comment thread .github/workflows/ci.yml
fi
- name: Cache git folder
uses: actions/cache@27d5ce7f107fe9357f9df03efb73ab90386fccae # v5
uses: actions/cache@55cc8345863c7cc4c66a329aec7e433d2d1c52a9 # v5

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 The pinned SHA now resolves to v6.1.0 (a major version bump), but the inline comment was not updated from # v5. This makes the comment misleading for anyone checking which version is actually pinned.

Suggested change
uses: actions/cache@55cc8345863c7cc4c66a329aec7e433d2d1c52a9 # v5
uses: actions/cache@55cc8345863c7cc4c66a329aec7e433d2d1c52a9 # v6.1.0
Prompt To Fix With AI
This is a comment left during a code review.
Path: .github/workflows/ci.yml
Line: 112

Comment:
The pinned SHA now resolves to `v6.1.0` (a major version bump), but the inline comment was not updated from `# v5`. This makes the comment misleading for anyone checking which version is actually pinned.

```suggestion
        uses: actions/cache@55cc8345863c7cc4c66a329aec7e433d2d1c52a9 # v6.1.0
```

How can I resolve this? If you propose a fix, please make it concise.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

Fix in Claude Code

@codacy-production

Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.

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