cache restore on versions 3 and 4 not working
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.6k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
The functionality of the cache action seems to be completely broken.
Configurations attempted:
- save/restore actions @v4
- save/restore actions @v3
- base cache action @v4
- base cache action @v3
Experimental Workflow and Results
The cache is being accessed on the same branch, in the same workflow (and later, if the first set of jobs pass).
These screenshots pertain to the run of base cache action @v3, they are consistent across all configurations.
Cache version 2 works as expected.
Would definitely prefer to use the most recent versions.
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 experimental workflow and results linked in the issue, then reproduce the reported behavior using the save/restore actions and base cache action at v3 and v4. Compare those runs with the v2 configuration, focusing on access from the same branch and workflow after the earlier jobs pass. Done means cache restore works consistently with the current supported version.
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
- 25/100