test: update chrome for testing example versions to 136.x

[MikeMcC399]

Situation

The script master/examples/chrome-for-testing/scripts/test.sh tests "Chrome for Testing" using versions:

'stable'
'beta'
'dev'
'canary'
'130'
'131.0.6778.204'

In the meantime, Cypress supports latest 3 browser versions. The current Chrome version is 136, meaning that the numerical versions used in the test are now unsupported.

The alias stable is always supported by Cypress. The other aliases beta, dev and canary give advance access to functionality that is planned to flow into a stable supported release.

Change

Update the numerical versions tested through master/examples/chrome-for-testing/scripts/test.sh to use current stable versions:

'136'
'136.0.7103.92'

[cypress-app-bot]

• Create a Draft Pull Request if your PR is not ready for review. Mark the PR as Ready for Review when you're ready for a Cypress team member to review the PR.

[MikeMcC399]

@AtofStryker

https://github.com/cypress-io/cypress-docker-images/actions/runs/15004681757/job/42160195940 shows

Chrome for Testing 137.0.7151.15

successfully running a smoke test with Cypress 14.0.0

so that's reassuring to know it's still working with the beta version!

[jennifer-shehane]

@MikeMcC399 Yes, we're really only expecting disruptions to the loading of Chrome extensions via our APIs or using the cypress/puppeteer package with Cypress.

[jennifer-shehane]

Thanks for bumping this!