build: bump actions/cache to v6 - #8
Open
lachieh wants to merge 1 commit into
Open
Conversation
actions/cache@v4 targets the deprecated Node 20 runtime, which GitHub now forces onto Node 24 and warns about on every run. v6 runs on the node24 runtime, eliminating the deprecation warning.
Contributor
|
no API key found — Pullfrog needs at least one LLM provider API key (e.g. To fix: add the key as a GitHub Actions secret (referenced from your workflow's Open repo secrets → · Configure model → · Setup docs → · Ask in Discord → |
|
@colinhacks could this be merged to enable better dev-exp. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

build: bump actions/cache to v6
GitHub deprecated the Node 20 runtime on runners. They now force anything still pinned to Node 20 to run on Node 24 anyway, so this isn't a functional break — the cache already runs on 24. The only thing we get is a deprecation warning on every run:
setup-nubwrapsactions/cachein its "Cache nub store" step, so every consumer inherits that warning (e.g. "Detect server changes / Node.js 20 is deprecated" in the murals.plus pipelines). This just bumps the embedded step fromactions/cache@v4toactions/cache@v6to silence it. Key, paths, and restore-keys are unchanged.