guessing new backend is case-sensitive in base image name?
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.6k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
an actions/cache/restore action started failing for me during the brownout. the only explanation I could guess was that actions/cache/save was running on macOS-13 whereas actions/cache/restore was running on macos-13. I didn't see this change documented anywhere in the migration guide; but also it seems easy enough to make the backend case-insensitive. Not sure if there's any reason not to do that? Or make runs-on case-sensitive.
https://github.com/unisonweb/unison/actions/runs/13251002645/job/37026161441
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 linked workflow run and compare the base image names used by actions/cache/restore and actions/cache/save; then read the migration guide for any documented naming change. Trace where the action backend interprets the macOS-13 label and clarify whether case normalization or case-sensitive runs-on behavior is intended. Done means the intended semantics are decided, the failing workflow behavior is covered, and the migration guide reflects the decision.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, macos, typescript
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100