You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The issue is a mismatch between the Playwright version and the expected browser version, as pointed out by @ozgursar.
Each version of Playwright needs specific versions of browser binaries to operate. You will need to use the Playwright CLI to install these browsers.
With every release, Playwright updates the versions of the browsers it supports, so that the latest Playwright would support the latest browsers at any moment. It means that every time you update Playwright, you might need to re-run the install CLI command.
Our cache currently contains v1223 browser and Playwright expects v1228 browser. I've been looking for a way to check whether browser support has changed, but I haven't found one yet. I am now leaning towards two possible approaches:
Remove the cache step
Just like the heading says, we can remove the cache step, Install Playwright system deps step and the conditionals. This means that the workflow will have to download the browser for each run. Personally, I don't have an issue with this since this runs once every week.
Flushing cache every two weeks
Using a similar method as the one in WordPress-Develop, where we can clear cache after two weeks. This will prevent the cache from going stale, but an issue might still occur if Playwright releases a new version a day after clearing and saving the cache.
I would like to hear your thoughts on this @juanmaguitar
Activity
3kori commentedon Jun 20, 2026
The issue is a mismatch between the Playwright version and the expected browser version, as pointed out by @ozgursar.
Our cache currently contains v1223 browser and Playwright expects v1228 browser. I've been looking for a way to check whether browser support has changed, but I haven't found one yet. I am now leaning towards two possible approaches:
Remove the cache step
Just like the heading says, we can remove the cache step, Install Playwright system deps step and the conditionals. This means that the workflow will have to download the browser for each run. Personally, I don't have an issue with this since this runs once every week.
Flushing cache every two weeks
Using a similar method as the one in WordPress-Develop, where we can clear cache after two weeks. This will prevent the cache from going stale, but an issue might still occur if Playwright releases a new version a day after clearing and saving the cache.
I would like to hear your thoughts on this @juanmaguitar
3kori commentedon Jun 20, 2026
I have deleted the current cache to make way for Monday's run before we reach a consensus on a fix for the issue.
ozgursar commentedon Jun 22, 2026
Thanks for working on this @3kori. As this workflow runs only once per week, I think removing the cache stop is better.
juanmaguitar commentedon Jun 22, 2026
I agree. Removing the cache makes sense 👍
Let's see how it goes later today.