Windows runner support for cache archives #5

Closed
opened 2026-06-16 17:54:53 +00:00 by stephen · 1 comment
Owner

Why

The action intentionally supports Linux/macOS only; Windows tar/path handling is not implemented. Windows support matters for Forgejo fleets with mixed runners.

Verified

  • MIGRATION.md explicitly says Windows tar/path handling is not implemented.
  • action.yml folds OS into cache version but implementation uses POSIX tar assumptions.
  • No existing cache-action issues are filed.

Build

  • Define Windows archive format/path semantics compatible with actions/cache expectations.
  • Add Windows CI or mock tests for path normalization and cross-OS disabled behavior.
  • Document limitations for cross OS archives.
## Why The action intentionally supports Linux/macOS only; Windows tar/path handling is not implemented. Windows support matters for Forgejo fleets with mixed runners. ## Verified - `MIGRATION.md` explicitly says Windows tar/path handling is not implemented. - `action.yml` folds OS into cache version but implementation uses POSIX tar assumptions. - No existing cache-action issues are filed. ## Build - Define Windows archive format/path semantics compatible with actions/cache expectations. - Add Windows CI or mock tests for path normalization and cross-OS disabled behavior. - Document limitations for cross OS archives.
Author
Owner

Parked. Windows cache archive support is real product surface, but this pass found no named Windows runner customer, active Fjord Windows runner lane, or current support incident. Revisit when Windows runners become part of the managed CI offer or a buyer blocks on mixed Windows/Linux cache behavior.

Parked. Windows cache archive support is real product surface, but this pass found no named Windows runner customer, active Fjord Windows runner lane, or current support incident. Revisit when Windows runners become part of the managed CI offer or a buyer blocks on mixed Windows/Linux cache behavior.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
rasterstate/cache-action#5
No description provided.