Multiple backend service versions used in same workflow execution
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.6k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
Yesterday our workflows started failing when some steps were unable to restore from cache. Rerunning the workflow with debugging enabled revealed that action/cache@v4 was using different versions of its backing service— sometimes v1, other times v2. It seems the failure occurs when one version of the backing service is used to save the cache, and another version is used to restore from cache.
All the steps in the workflow are using the same version of the action (v4).
Incidentally, downgrading to action/cache@v4.1.2 seemed to solve the problem, but that version is deprecated and so was affected by the brownout today.
Here the cache is initialized with v1
… later in the same run
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 by reproducing the workflow with debugging enabled and compare the backend service versions used when saving and restoring through action/cache@v4. Done means a single workflow execution consistently uses the same backing-service version for both operations; the issue does not name a source file or test to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100