Mike McCready

[cypress-io/github-action > README > Parallel](https://github.com/cypress-io/github-action/blob/master/README.md#parallel) now contains the specific advice: "During staged rollout of a new GitHub-hosted runner version, GitHub may provide a mixture of current and new image versions...

Cypress documentation [Specifying Browsers in Parallel Builds](https://docs.cypress.io/guides/continuous-integration/github-actions#Specifying-Browsers-in-Parallel-Builds) now describes precautions to prevent this issue causing errors:  GitHub runners are currently preparing to update from Google Chrome `112.0.5615.165` to `113.0.5672.63`....

The workaround of using a [Cypress Docker image](https://docs.cypress.io/guides/continuous-integration/github-actions#Testing-with-Cypress-Docker-Images) is only available for Ubuntu / Linux on GitHub. These are the only operating systems supported as containers on GitHub. Windows and...

- According to the feedback in the GitHub actions/runner issue https://github.com/actions/runner/issues/2812#issuecomment-1708710610 no change can be expected in the way that GitHub Actions Backend randomly assigns image versions in response to...

https://docs.cypress.io/guides/guides/launching-browsers#WebKit-Experimental now recommends installing `npm install --save-dev [email protected]` due to issues with later versions.

Hi @wlsf82 > but is there an intention of fixing it at some point in the future? Or will we have to stay with 1.34 forever? - My understanding from...

I had a look at adding `webkit` to the set of browser examples on [cypress-io/github-action](https://github.com/cypress-io/github-action) to establish a baseline, however the `webkit` implementation seems to be more on the experimental...

@mkascel > ... or if the solution in the works is targeting GHA only. I haven't seen anything so far to indicate that a solution would only work on GitHub...

Testing on - Ubuntu `22.04.4` LTS - Node.js `v20.11.1` LTS - Cypress `13.6.6` ```shell npx cypress run --e2e --browser webkit ``` After executing the above command, Cypress incorrectly launches in...

@tchaton Have you considered using `cy.now()` https://docs.cypress.io/guides/guides/debugging#Run-Cypress-command-outside-the-test - (Note there is an open PR proposing to correct the example. See https://github.com/cypress-io/cypress-documentation/pull/5359)