Update browser support of Cypress to last 3 major versions

[MikeMcC399]

What would you like?

• Remove support for Chrome 64 - 79
• Make Chrome 80 minimum version

Why is this needed?

According to feedback in cypress-io/cypress-documentation#5104 (comment) from @mike-plummer Chrome 80 is needed for cypress open whereas Chrome 64 is sufficient for cypress run.

• Chrome itself only supports the stable version (see https://chromereleases.googleblog.com/ for releases) - currently 127.x
• Chrome 64 was released in Jan 2018
• Chrome 80 was released in Feb 2020

Cypress 13 enforces a minimum of Chrome 64:

cypress/packages/launcher/lib/known-browsers.ts

Lines 3 to 4 in ef7db3d

	// Chrome started exposing CDP 1.3 in 64
	export const MIN_CHROME_VERSION = 64

For consistent and simplified clarity of supported Chrome version, Chrome 80 should be made the minimum testable browser version.

Other

• Relates to Cypress 14: Breaking changes #29925
  Follows on from
• Conflicting information for minimum Chrome version 64 or 80 cypress-documentation#5446 (comment)
• Cypress 14: Breaking changes #29925 (comment)

[MikeMcC399]

• According to smoke-tests in Error Runtime.addBinding with Chromium 66 #30205 (comment), Cypress 11.x seems to be the last version which worked with Chromium 64 -79.

[jennifer-shehane]

We decided that moving forward, after Cypress 14, we will only officially support the last 3 major versions, from stable for all browsers (excluding Webkit which has a static version). So if the stable release of Chrome is at 129, we would officially support Chrome 127, 128, and 129.

We will update the docs to reflect this.

Additionally, we will remove the warning on browsers that are under the 'minimum' within the product, as this will be a moving target and does not gaurantee that Cypress WILL NOT work in earlier versions. It may work in earlier versions and we'll do our best to not use newer APIs that could break people using Cypress, but we will not triage or prioritize issues running browsers beyond 3 major versions after Cypress 14.

[MikeMcC399]

@jennifer-shehane

• For Chromium-family and Firefox that sounds like a good approach. It ties in with what the browser owners support.

• WebKit is a special case and due to WebKit 18 fails driver-integration-tests-webkit (cookies.cy.js) #29973 & Update WebKit testing to 18.x #29954 it is unclear what Cypress is currently supporting. v16 is configured. v17 and v18 fail internal tests.