Skip to content

chore(deps): bump actions/cache from 3 to 5#116

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

chore(deps): bump actions/cache from 3 to 5#116
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/actions/cache-5

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jun 10, 2026

Copy link
Copy Markdown
Contributor

Bumps actions/cache from 3 to 5.

Release notes

Sourced from actions/cache's releases.

v5.0.0

[!IMPORTANT] actions/cache@v5 runs on the Node.js 24 runtime and requires a minimum Actions Runner version of 2.327.1.

If you are using self-hosted runners, ensure they are updated before upgrading.

What's Changed

Full Changelog: actions/cache@v4.3.0...v5.0.0

v4.3.0

What's Changed

New Contributors

Full Changelog: actions/cache@v4...v4.3.0

v4.2.4

What's Changed

New Contributors

Full Changelog: actions/cache@v4...v4.2.4

v4.2.3

What's Changed

  • Update to use @​actions/cache 4.0.3 package & prepare for new release by @​salmanmkc in actions/cache#1577 (SAS tokens for cache entries are now masked in debug logs)

New Contributors

Full Changelog: actions/cache@v4.2.2...v4.2.3

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

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

  • Bump @actions/cache to v5.0.3 #1692

5.0.1

  • Update @azure/storage-blob to ^12.29.1 via @actions/cache@5.0.1 #1685

5.0.0

[!IMPORTANT] actions/cache@v5 runs on the Node.js 24 runtime and requires a minimum Actions Runner version of 2.327.1.

... (truncated)

Commits
  • 27d5ce7 Merge pull request #1747 from actions/yacaovsnc/update-dependency
  • f280785 licensed changes
  • 619aeb1 npm run build generated dist files
  • bcf16c2 Update ts-http-runtime to 0.3.5
  • 6682284 Merge pull request #1738 from actions/prepare-v5.0.4
  • e340396 Update RELEASES
  • 8a67110 Add licenses
  • 1865903 Update dependencies & patch security vulnerabilities
  • 5656298 Merge pull request #1722 from RyPeck/patch-1
  • 4e380d1 Fix cache key in examples.md for bun.lock
  • 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)

@dependabot
chore(deps): bump actions/cache from 3 to 5
f9a5cd2 
Bumps [actions/cache](https://github.com/actions/cache) from 3 to 5.
- [Release notes](https://github.com/actions/cache/releases)
- [Changelog](https://github.com/actions/cache/blob/main/RELEASES.md)
- [Commits](actions/cache@v3...v5)

---
updated-dependencies:
- dependency-name: actions/cache
  dependency-version: '5'
  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 Jun 10, 2026
This was referenced Jun 18, 2026
Closed
Merged
@wiiiimm

wiiiimm commented Jun 18, 2026

Copy link
Copy Markdown
Owner

Superseded by #131, which consolidates all open Dependabot updates into a single PR. Closing in favour of that.

@wiiiimm wiiiimm closed this Jun 18, 2026
@dependabot @github

dependabot Bot commented on behalf of github Jun 18, 2026

Copy link
Copy Markdown
Contributor Author

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

@dependabot dependabot Bot deleted the dependabot/github_actions/actions/cache-5 branch June 18, 2026 06:05
wiiiimm added a commit that referenced this pull request Jun 18, 2026
@wiiiimm @claude
chore(deps): consolidate open dependabot updates (GMC-45) [semantic p…
d548f24 
…r title] (#131)

* chore(deps): consolidate open dependabot updates (GMC-45)

Combine all 13 open Dependabot PRs (#116–#129) into a single update.

npm group (#129): @octokit/graphql 9.0.3, apollo3-cache-persist 0.15.0,
chalk 5.6.2, dotenv 17.4.2, fuse.js 7.4.2, react 19.2.7,
@types/react 19.2.17, tsup 8.5.1, vitest 4.1.9.

npm majors: typescript 6.0.3 (#128), @vitest/coverage-v8 4.1.8 (#127),
semantic-release 25.0.5 (#126), ink-testing-library 4.0.0 (#125),
env-paths 4.0.0 (#124), @types/node 25.9.2 (#123), open 11.0.0 (#122).

GitHub Actions: setup-node v6 (#120), checkout v6 (#119),
github-script v9 (#118), download-artifact v8 (#117), cache v5 (#116).

Verified: typecheck (TS 6), build, and full test suite (456/456) all pass.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* ci: bump release workflow to Node 22 for semantic-release 25 (GMC-45)

semantic-release 25 requires Node ^22.14.0 || >=24.10.0; the release
workflow still set up Node 20, which would fail `npx semantic-release`
on the next push to main. Bump all setup-node steps to Node 22 (LTS).

Flagged by Cursor Bugbot (High) and Codex (P1) on PR #131.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* chore: raise Node floor to >=20 for env-paths 4 and open 11 (GMC-45)

env-paths@4 and open@11 both declare engines.node ">=20", but the
package still advertised ">=18", letting Node 18-19 users install a
build that breaks at startup (env-paths) and on browser open (open).
Align engines.node and the setup docs to >=20. Node 18 is already EOL.

Flagged by Cursor Bugbot (Medium) on PR #131.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* build: migrate to @yao-pkg/pkg and target node20 binaries (GMC-45)

vercel/pkg (pkg@5.8.1) is archived and only ships base binaries up to
Node 18, so release binaries embedded a Node 18 runtime — incompatible
with env-paths 4 / open 11 (Node 20+) after raising the engine floor.
Switch to the maintained @yao-pkg/pkg fork and build node20 targets in
both the build:binaries script and the release workflow. The packager
needs Node 22 to run, which the release jobs already use.

Flagged by Cursor Bugbot (High) on PR #131.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* docs: note build:binaries requires Node 22+ for @yao-pkg/pkg (GMC-45)

The CLI runtime engine stays at Node >=20, but @yao-pkg/pkg requires
Node >=22 to run. Document this in the Packaging section so contributors
on Node 20/21 know the binary build needs a newer Node, rather than
raising engines.node and wrongly forcing end users onto Node 22.

Addresses CodeRabbit engine-mismatch note on PR #131. The companion
"Invalid Windows pkg target" finding is a false positive: pkg-fetch's
toFancyPlatform aliases "windows" -> "win" during target parsing.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

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

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@wiiiimm