v4 not using the new cache service
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.6k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
Using the last version of the actions/cache we have started to receive the following error:
Failed to save: Unable to reserve cache with key ....., another job may be creating this cache. More details: This legacy service is shutting down, effective April 15, 2025. Migrate to the new service ASAP. For more information: https://gh.io/gha-cache-sunset
Warning: Cache save failed.
The error references the already announced service deprecation. However, using @v4 according to the documentation (or even specifying the last 4.2.3 release), it must work with the new service API.
Is there anything to change/update to start using the new API?
Thanks in advance!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the actions/cache @v4 documentation and the 4.2.3 release referenced in the issue, then reproduce the reported cache-save warning. Determine whether the action is actually using the new cache service and identify the repository entry point that controls that behavior. Done means the warning no longer occurs and cache saves use the new service.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100