I updated the caching action to v2 and cache instead of node_modules the NPM cache directory which is recommend see here. Caching the node_modules folder can lead to the behaviour which you've experienced that you need to install Cypress or Playwright manually again with npm install.
Also I switched to npm ci instead of npm install which is optimised to run on bots. This will strictly use the package-lock.json and always install the pinned version. (Test run). Also using now pull request triggers too so external contributors will trigger the bots.
Hi Umar,
related to that (https://github.com/microsoft/playwright/issues/3712) issue I followed up with adjusting your caching strategy with GitHub Actions.
I updated the caching action to v2 and cache instead of node_modules the NPM cache directory which is recommend see here. Caching the node_modules folder can lead to the behaviour which you've experienced that you need to install Cypress or Playwright manually again with npm install.
Also I switched to
npm ci
instead ofnpm install
which is optimised to run on bots. This will strictly use the package-lock.json and always install the pinned version. (Test run). Also using now pull request triggers too so external contributors will trigger the bots.The failing bots seem unrelated.