Files
cloudflare__vinext/.github
James Anderson fe700996d9 ci: extract Playwright cache plumbing into a composite action (#1438)
Two workflows now share an identical playwright-version + cache-restore
pattern: ci.yml (which owns the cache, used by E2E jobs) and
nextjs-deploy-suite.yml (which restores it read-only, added in #1435).
Pull the duplication into .github/actions/playwright-cache so the cache
key format can't drift between the two callers — if it ever does, the
deploy-suite stops hitting ci.yml's cache and the upstream Playwright
extraction hang from 2026-05-22 (runs 26265986264 .. 26281758803)
reappears.

The composite action:
- Reads the playwright version from a configurable lockfile path
  (`lockfile` input, defaults to pnpm-lock.yaml).
- Restores ~/.cache/ms-playwright keyed
  `playwright-${browser}-${runner.os}-v${version}`.
- Supports two modes: `cache` (restore + save, default — for the workflow
  that owns the cache) and `restore` (read-only — for downstream
  consumers that don't want to fight over the save).
- Exposes `cache-hit`, `version`, and `key` outputs so callers can gate
  install steps or use the version for sibling cache keys (e.g. ci.yml's
  apt-archives cache for WebKit deps).

No behavioural change — same cache keys, same restore-keys, same
~/.cache/ms-playwright path.
2026-05-22 11:15:37 +00:00
..
2026-03-09 14:56:14 +00:00
2026-02-24 09:29:39 -06:00