Skip to content

chore: update cypress to 16.2.1 - #1015

Merged
jennifer-shehane merged 3 commits into
masterfrom
chore/update-cypress-16
Nov 2, 2026
Merged

jennifer-shehane merged 3 commits into
masterfrom
chore/update-cypress-16

Conversation

@jennifer-shehane

@jennifer-shehane jennifer-shehane commented Nov 2, 2026 •

Copy link
Copy Markdown
Member
  • Closes N/A

Additional details

This moves the repo's Cypress dev dependency from ^15.10.0 to ^16.2.1 and cleans up what the Cypress 16 migration guide asks for.

  • package.json / package-lock.json: the cypress dev dependency changes to ^16.2.1. Every other lockfile change is inside Cypress's own dependency tree.
  • Test app configs: removes allowCypressEnv: false from all 20 test-apps/*/cypress.config.js. Cypress 16 removed the option and warns when it's set.
  • component-vite test app: moves to vite@^8.3.5 and vite-plugin-istanbul@^9.0.1. Cypress 16 component testing requires Vite 8 and throws ViteVersionNotSupportedError on Vite 7, and vite-plugin-istanbul 7.x only supports up to Vite 7. @vitejs/plugin-react 5.2 already accepts Vite 8, so it stays.
  • README: the 3.x → 4.x migration note now says Cypress.env() was removed in Cypress 16, not that it "will be."

What doesn't need changing:

  • The plugin already reads its options from Cypress.expose(). Nothing in lib/, middleware/, or the test apps calls Cypress.env().
  • Nothing uses cy.end(), cy.exec(), execTimeout, the removed experimental options, runtime Cypress.config() changes to the viewport or blockHosts, or .coffee files.
  • No --env flags or plugin-option CYPRESS_* variables in CI or scripts. The CYPRESS_* variables in CI are install settings only.
  • peerDependencies (cypress >=15.10.0) and engines (node >=20) are untouched, so the plugin still installs for Cypress 15 users. CI already runs on Node 22 and 24, which Cypress 16 requires.

Known open item: every test app runs in the default Electron browser, which Cypress 16 marks as deprecated, so each run prints a warning. Switching to defaultBrowser: 'chrome' would clear it, but it changes what CI exercises (Chrome now uses Cypress 16's native network handling), so it's left for a follow-up decision.

Steps to test

  1. npm ci && npm run build
  2. npm test and npm run format:check. Both pass locally.
  3. npx cypress verify, then npm run apps:test:coverage:verify. Locally, all 20 test apps pass on Cypress 16.2.1 with their coverage checks; component-vite passes at 100% after the Vite 8 update.

How has the user experience changed?

No change. The published plugin's code and its supported Cypress and Node ranges are the same; this only updates the Cypress version used to develop and test it.

🤖 Generated with Claude Code

https://claude.ai/code/session_01WUv8r4ui43Dk3dtH6nGpTg

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WUv8r4ui43Dk3dtH6nGpTg
Cypress 16 removed the option and warns when it is set.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WUv8r4ui43Dk3dtH6nGpTg
Cypress 16 component testing requires Vite 8. vite-plugin-istanbul 7.x
only supports up to Vite 7, so it moves to 9.x.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WUv8r4ui43Dk3dtH6nGpTg
@jennifer-shehane
jennifer-shehane merged commit b0cf1df into master Nov 2, 2026
31 checks passed
@jennifer-shehane
jennifer-shehane deleted the chore/update-cypress-16 branch November 2, 2026 02:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants