Caching the Playwright browsers is a concept which often leads to confusion, since yes, browsers can be cached, but they also rely on operating system dependencies, which can't be cached.
This might work for Chromium, since GitHub Action environments have all the OS dependencies already pre-installed for running Chromium, but for WebKit / Firefox this won't work (launch will yell with dependencies missing error).
So having this extra complexity for saving 1-5 seconds on a process (downloading the browsers) which only takes 5 seconds seems not worth it (restoring the cache takes a similar duration)
Caching the Playwright browsers is a concept which often leads to confusion, since yes, browsers can be cached, but they also rely on operating system dependencies, which can't be cached.
This might work for Chromium, since GitHub Action environments have all the OS dependencies already pre-installed for running Chromium, but for WebKit / Firefox this won't work (launch will yell with dependencies missing error).
So having this extra complexity for saving 1-5 seconds on a process (downloading the browsers) which only takes 5 seconds seems not worth it (restoring the cache takes a similar duration)
See also here: https://playwright.dev/docs/ci#caching-browsers