cypress
16.3.0 · 10 Nov 2026MIT7.6M / weekRepositoryHomepagenpmAtom feed
Upgrading cypress From 7.7.0 to 16.3.0
170 releases in betweennotes for 66
Reading releases, release notes and advisories…
- 45+
- changes to make
- 0
- advisories fixed
- 80+
- new
- 247+
- fixes
Counted from 66 of 170 release notes. Advisories are counted from the advisory database, in full.
Start here
Before you upgrade
Tick each one off as you go- Breaking16.0.0
- Breaking16.0.0
- Breaking16.0.0
- Breaking16.0.0
- Breaking16.0.0
- Breaking16.0.0
- Breaking16.0.0
- Breaking16.0.0
- Breaking16.0.0
- Breaking15.0.0
Security
- 16.3.0
Upgraded
electronfrom41.7.0to43.8.4to address the compromised eMudhra intermediate certificates vulnerability reported in security scans. Connections that Cypress makes itself, such as to Cypress Cloud, now reject certificates issued through these intermediates. Node code in the config process, such as setupNodeEvents, runs on the Node.js version that runs thecypressCLI, so it needs a Node.js release that includes the same fix. Addresses #35124. - 16.3.0
Upgraded
systeminformationto5.33.18to address the SNYK-JS-SYSTEMINFORMATION-21771271 (CVE-2026-116576) vulnerability reported in security scans. Addresses #35196. - 16.3.0
Upgraded
node-forgefrom1.4.0to1.4.3to address the Improper Certificate Validation vulnerability reported in security scans. Addressed in #35279. - 16.3.0
Upgraded
jimpfrom0.22.12to1.6.1to address an infinite loop vulnerability (CVE-2026-31808) in itsfile-typedependency reported in security scans. This also removesxml2js0.4.23, which has a prototype pollution vulnerability (CVE-2023-0842). Addresses #35271. - 16.2.0
Upgraded
shell-quotefrom1.10.0to1.11.0to address a Command Injection vulnerability reported in security scans.shell-quoteis a transitive dependency oflaunch-editor. Addressed in #34960. - 15.18.0
Upgraded
undicifrom6.26.0to6.27.0to address a CRLF Injection vulnerability reported in security scans. Addressed in #34121. - 15.16.0
Upgraded
esbuildto^0.28.0to address CVE-2025-68121 in the bundledesbuildGo binary (incorrect TLS certificate validation during session resumption), as reported in container and image security scans. Fixes #33599. Addressed in #33816. - 15.15.0
Upgraded
socket.iofrom4.0.1to4.8.3,socket.io-clientfrom4.0.1to4.8.3, andsocket.io-parserfrom4.0.5to4.2.6to address a Denial of Service vulnerability reported in security scans. Theengine.io,engine.io-client, andengine.io-parserdirect deps in@packages/socketwere also bumped to keep transitive copies aligned and the existing browser-side patches applied. Addressed in #33719. - 15.15.0
Upgraded
uuidfrom8.3.2to11.1.1to address an Improper Validation of Specified Index, Position, or Offset in Input vulnerability reported in security scans. Addressed in #33765. - 15.14.0
Upgraded
axiosto1.15.0to address CVE-2025-62718 and CVE-2026-40175 vulnerabilities reported in security scans. Fixes #33590.
Release by release
- Security
Upgraded
electronfrom41.7.0to43.8.4to address the compromised eMudhra intermediate certificates vulnerability reported in security scans. Connections that Cypress makes itself, such as to Cypress Cloud, now reject certificates issued through these intermediates. Node code in the config process, such as setupNodeEvents, runs on the Node.js version that runs thecypressCLI, so it needs a Node.js release that includes the same fix. Addresses #35124. - Security
Upgraded
systeminformationto5.33.18to address the SNYK-JS-SYSTEMINFORMATION-21771271 (CVE-2026-116576) vulnerability reported in security scans. Addresses #35196. - Security
Upgraded
node-forgefrom1.4.0to1.4.3to address the Improper Certificate Validation vulnerability reported in security scans. Addressed in #35279. - Security
Upgraded
jimpfrom0.22.12to1.6.1to address an infinite loop vulnerability (CVE-2026-31808) in itsfile-typedependency reported in security scans. This also removesxml2js0.4.23, which has a prototype pollution vulnerability (CVE-2023-0842). Addresses #35271.
- Security
16.2.1no release note
- Security
Upgraded
shell-quotefrom1.10.0to1.11.0to address a Command Injection vulnerability reported in security scans.shell-quoteis a transitive dependency oflaunch-editor. Addressed in #34960. - New
Added the cy.getByRole() query, which finds elements by their ARIA role and, optionally, their accessible name, for example
cy.getByRole('tab', { name: 'Billing' }). Elements hidden from the accessibility tree are skipped unless you pass{ hidden: true }. For a role that HTML has an element for, only that element matches by default, socy.getByRole('button')finds a<button>but not a<div role="button">. Pass{ native: false }to also match elements with aroleattribute. Like cy.get(), it yields every match and retries until its assertions pass. When nothing matches, the error lists the roles and accessible names on the page. Addressed in #34937. - Fixed
Fixed a regression in 16.0.0 where a configured clientCertificates entry was not presented for requests the browser issued in Chrome, Chromium, and Edge, so an origin requiring mutual TLS showed a certificate prompt in
cypress openand hung incypress run. Fixes #34807. - Fixed
Fixed a regression in 15.20.0 where a cookie changed by cy.request() or cy.setCookie() was sent to the server with its earlier value on the next navigation of the application under test, even though cy.getCookie() reported the new one. Fixes #34891.
- Security
16.1.1no release note
- New
Added the trustedCertificates configuration option. On the native browser network path (Chrome, Chromium, and Edge), declare a certificate your application under test presents — a self-signed development certificate, an internal certificate authority, or a precomputed SPKI fingerprint — and Chrome treats connections to that origin as trusted rather than merely tolerating its certificate errors. Static assets from the origin are then cached across navigations as they are in production; previously nothing from an untrusted-certificate origin was ever written to the browser's disk cache, so asset-heavy specs re-downloaded every asset on each cy.visit(). Origins you do not declare continue to load exactly as before. Firefox, WebKit, Electron, and forceHttp1 runs are unaffected. Addresses #34760.
- Fixed
Fixed a memory leak in the Cypress server where every service worker started by the application under test held onto state until the browser closed, so memory use climbed over the course of a run in Chrome, Chromium, Edge, and Electron. Addressed in #34721.
- Fixed
Fixed a regression in 16.0.0 where a run in Chrome, Chromium, or Edge could stop producing output partway through and hang indefinitely, with no error, no failing test, and no timeout, until the CI job was killed for exceeding its no-output limit. Fixes #34778.
- Fixed
Fixed an issue where adding a
--disable-featuresargument in before:browser:launch silently dropped every feature Cypress disables in Chrome, Chromium, and Edge, because the browser honors only the last occurrence of that argument. Cypress now merges its own values with yours. Fixes #34775. - Fixed
Fixed an issue where a variant of A/B tested content in the Cypress app that was weighted never to be shown could become the only variant shown. Fixes #34814.
- Fixed
Fixed a regression in 12.0.0 where an assertion on a cy.contains() command that matched no element did not say what was searched for, reporting
expected undefined not to exist in the DOMin the Command Log. The searched content is now shown, such asexpected Saving not to exist in the DOM. Fixes #25962. - Fixed
- New
- Breaking
Faster tests, less flake, and a few breaking changes that may require updates.
- Breaking
- Breaking
Removed the
cy.end()command, which ended a chain of commands by yieldingnull. A Cypress chain is already terminated when the nextcy.<command>()starts a new chain, so existing.end()calls can simply be removed. See the Migration Guide. Addressed in #33696. - Breaking
Removed the
experimentalSourceRewritingconfiguration option. The default regex-based source rewriting handles every case the AST-based rewriter did, so default behavior is unchanged and the option can be deleted from your config. If you were using it to work around Subresource Integrity errors, enable removeSRIAttributes instead. See the Migration Guide. Addresses #34213.
- Breaking
15.21.1 – 15.21.22 releases, no release note
- Deprecated
cy.exec()has been deprecated and will be removed in a future major release of Cypress. Use cy.task() instead, which runs in Node without depending on the operating system, shell, or terminal of the machine running Cypress. The execTimeout configuration option is deprecated alongside it, in favor of taskTimeout. Addresses #34639. - New
Added a
CYPRESS_DISABLE_GUEST_TELEMETRYenvironment variable, which disables any reporting Cypress sends for non-logged sessions. This includes anonymous usage events within Cypress open-mode and the Cypress CLI. Addressed in #34540. - Fixed
- Fixed
Fixed an issue where overriding blockHosts with test configuration (for example
describe('...', { blockHosts: [...] }, ...)) had no effect, so requests were still blocked or allowed according to the project-level value. Test-levelblockHostsoverrides now take effect at runtime and are restored between specs. Fixes #21151.
- Deprecated
360 other lines we could not sort, mostly version bumps
- 16.3.0
In
cypress run, specs now start sooner when Cypress launches a new browser for them. In Electron, this is every spec unless component testing'sexperimentalSingleTabRunModeis enabled. In other browsers, it is the first spec and any spec after the browser exits unexpectedly. Fixed in #35186. - 16.3.0
The Cypress binary no longer includes a copy of TypeScript that it never used, since Cypress loads TypeScript from your project. This makes the download smaller and takes less disk space once installed. On Linux arm64, Cypress also starts faster, because it no longer tries to load TypeScript as it launches. Fixed in #35184.
- 16.3.0
cypress runnow spends less time finding the browsers installed on your machine before it starts the first spec, so runs start sooner. Fixed in #35181. - 16.3.0
Installing the Cypress binary from an interactive terminal, such as with
npx cypress install, now finishes unzipping sooner and uses less CPU, especially on Windows. Installs in CI, and package manager installs that run without a terminal, are unchanged. Fixed in #35243. - 16.3.0
Registering the same event more than once in setupNodeEvents now runs every handler in registration order, instead of only the last one, for before:run, after:run, before:spec, after:spec, before:browser:launch, and after:screenshot.
before:browser:launchandafter:screenshothandlers each receive the result of the handler before them. If a handler throws, later handlers do not run. If you re-registered one of these events to replace a plugin's handler, both now run; to keep only yours, pass the plugin anonthat skips that event. Addresses #5240, #19809 and #27524. - 16.3.0
The error shown when Cypress cannot start on Linux because of a missing system library now lists each library and the package that provides it, and a missing or failing Xvfb now shows install commands or the likely causes. Addressed in #35116.
- 16.3.0
cypress opennow prints configuration errors and warnings, including the stack trace of a config file that fails to load, to the terminal. Previously they only appeared in the Cypress window, so a script or AI agent runningcypress opensaw nothing while it waited. Fixed in #35104. - 16.3.0
cypress open --project <path> --e2e --browser <browser>run by an AI coding agent now launches the browser without waiting for the welcome screen to be dismissed in the Cypress window. SetCYPRESS_AGENT_MODE=1to force this behavior for an agent Cypress does not detect, orCYPRESS_AGENT_MODE=0to turn it off. Fixed in #35105. - 16.3.0
cypress open --e2e --project <path>run by an AI coding agent in a project with no Cypress configuration file now creates the configuration and support files and starts the project in one launch, and prints the files it created. Previously the project did not start until Continue was pressed in the Cypress window. Fixed in #35106. - 16.3.0
cypress tap statusnow reports anerrorstage, with the reason, whencypress opencould not load the project, for example because the configuration file has a syntax error, and the othercypress tapcommands say that the project could not load instead of that no session is running. Previouslycypress tap statusreportednot connected. Fixed in #35107.
8 internal lines (docs, tests, tooling) left out.
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.