restore-keys omitted from Resolved Keys array in self-hosted container job
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.6k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
restore-keys value is correctly shown in resolved 'with:' block but does not appear in the internal Resolved Keys array logged before the cache lookup request. Reproduced consistently across actions/cache@v6, v6.1.0, self-hosted runner, container: job.
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
Reproduce the issue using actions/cache@v6 or v6.1.0 in a self-hosted container job, then trace how the resolved 'with:' values become the internal Resolved Keys array before the cache lookup request. Done means restore-keys appears in that array and the behavior is covered by an appropriate regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100