Packages

cypress

16.3.0 · 10 Nov 2026MIT7.6M / weekRepositoryHomepagenpmAtom feed

Upgrading cypress From 16.1.1 to 16.3.0

3 releases in betweennotes for 2

Reading releases, release notes and advisories…

  1. 16.1.1yours
  2. 16.2.0security
  3. 16.2.1
  4. 16.3.0target
?
changes to make
0
advisories fixed
1+
new
27+
fixes

Counted from 2 of 3 release notes. Advisories are counted from the advisory database, in full.

Security

  • Upgraded electron from 41.7.0 to 43.8.4 to 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 the cypress CLI, so it needs a Node.js release that includes the same fix. Addresses #35124.

    16.3.0
  • Upgraded systeminformation to 5.33.18 to address the SNYK-JS-SYSTEMINFORMATION-21771271 (CVE-2026-116576) vulnerability reported in security scans. Addresses #35196.

    16.3.0
  • Upgraded node-forge from 1.4.0 to 1.4.3 to address the Improper Certificate Validation vulnerability reported in security scans. Addressed in #35279.

    16.3.0
  • Upgraded jimp from 0.22.12 to 1.6.1 to address an infinite loop vulnerability (CVE-2026-31808) in its file-type dependency reported in security scans. This also removes xml2js 0.4.23, which has a prototype pollution vulnerability (CVE-2023-0842). Addresses #35271.

    16.3.0
  • Upgraded shell-quote from 1.10.0 to 1.11.0 to address a Command Injection vulnerability reported in security scans. shell-quote is a transitive dependency of launch-editor. Addressed in #34960.

    16.2.0

Release by release

  1. 16.3.0

    Security fix10 Nov 202620 fixes
    • Security

      Upgraded electron from 41.7.0 to 43.8.4 to 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 the cypress CLI, so it needs a Node.js release that includes the same fix. Addresses #35124.

    • Security

      Upgraded systeminformation to 5.33.18 to address the SNYK-JS-SYSTEMINFORMATION-21771271 (CVE-2026-116576) vulnerability reported in security scans. Addresses #35196.

    • Security

      Upgraded node-forge from 1.4.0 to 1.4.3 to address the Improper Certificate Validation vulnerability reported in security scans. Addressed in #35279.

    • Security

      Upgraded jimp from 0.22.12 to 1.6.1 to address an infinite loop vulnerability (CVE-2026-31808) in its file-type dependency reported in security scans. This also removes xml2js 0.4.23, which has a prototype pollution vulnerability (CVE-2023-0842). Addresses #35271.

  2. 16.2.1no release note

  3. 16.2.0

    Security fix14 Oct 20261 new · 7 fixes
    • Security

      Upgraded shell-quote from 1.10.0 to 1.11.0 to address a Command Injection vulnerability reported in security scans. shell-quote is a transitive dependency of launch-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, so cy.getByRole('button') finds a <button> but not a <div role="button">. Pass { native: false } to also match elements with a role attribute. 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 open and hung in cypress 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.

20 other lines we could not sort, mostly version bumps
  • In cypress run, specs now start sooner when Cypress launches a new browser for them. In Electron, this is every spec unless component testing's experimentalSingleTabRunMode is 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 run now 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:launch and after:screenshot handlers 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 an on that 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 open now 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 running cypress open saw 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. Set CYPRESS_AGENT_MODE=1 to force this behavior for an agent Cypress does not detect, or CYPRESS_AGENT_MODE=0 to 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 status now reports an error stage, with the reason, when cypress open could not load the project, for example because the configuration file has a syntax error, and the other cypress tap commands say that the project could not load instead of that no session is running. Previously cypress tap status reported not connected. Fixed in #35107.

    16.3.0

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.