Repository navigation
Conversation
|
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. |
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.
edc5c00 to
f9680ba
Compare
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes: this PR moves the embedded "Cache nub store" step to actions/cache@v6. I checked the bump against the upstream contract at the v6 tag.
- Bumped
actions/cachefromv4tov6inaction.yml. Upstreamv6/action.ymlruns onnode24and keeps thepath/key/restore-keysinputs that setup-nub passes.v6/src/restoreImpl.tsstill setscache-hitto'true'on an exact hit and'false'on arestore-keyshit, and leaves it unset on a full miss. The documentedcache-hitoutput that setup-nub re-exports therefore stays accurate. The v6.0.0 and v6.1.0 release notes list only internal changes: an ESM migration and handling for read-only cache access.
claude-opus-5-5 | 𝕏

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.