Packages

cypress

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

Upgrading cypress From 12.13.0 to 12.17.4

8 releases in betweennotes for 4

Reading releases, release notes and advisories…

Other targets from 12.13.0Latest16.3.0
?
changes to make
0
advisories fixed
2+
new
10+
fixes

Counted from 4 of 8 release notes. Advisories are counted from the advisory database, in full.

Security

  • Upgraded find-process from 1.4.1 to 1.4.7 to address this Snyk security vulnerability. Addressed in #26906.

    12.14.0
  • Upgraded firefox-profilefrom 4.0.0 to 4.3.2 to address security vulnerabilities within sub-dependencies. Addressed in #26912.

    12.14.0

Release by release

  1. 12.17.1 – 12.17.44 releases, no release note

  2. 12.17.0

    6 Jul 20237 fixes
    • Fixed

      Fixed issues where commands would fail with the error must only be invoked from the spec file or support file. Fixes #27149 and #27163.

    • Fixed

      Fixed a regression introduced in Cypress 12.12.0 where Cypress may fail to reconnect to the Chrome DevTools Protocol in Electron. Fixes #26900.

    • Fixed

      Fixed an issue where chrome was not recovering from browser crashes properly. Fixes #24650.

    • Fixed

      Fixed a race condition that was causing a GraphQL error to appear on the Debug page when viewing a running Cypress Cloud build. Fixed in #27134.

    • Fixed

      Fixed a race condition in electron where the test window exiting prematurely during the browser launch process was causing the whole test run to fail. Addressed in #27167.

    • Fixed

      Fixed minor issues with TypeScript types in the CLI. Fixes #24110.

    • Fixed

      Fixed an issue where a value for the Electron debug port would not be respected if defined using the ELECTRON_EXTRA_LAUNCH_ARGS environment variable. Fixes #26711.

  3. 12.16.0

    26 Jun 20231 new · 1 fix
    • New

      Added support for Angular 16.1.0 in Cypress Component Testing. Addresses #27049.

    • Fixed

      Fixed an issue where certain commands would fail with the error must only be invoked from the spec file or support file when invoked with a large argument. Fixes #27099.

  4. 12.15.0

    20 Jun 20231 new · 1 fix
    • New

      Added support for running Cypress tests with Chrome's new --headless=new flag. Chrome versions 112 and above now run in the headless mode that matches the headed browser implementation. Addresses #25972.

    • Fixed

      Fixed an issue where video output was not being logged to the console when videoCompression was turned off. Videos now log to the terminal regardless of the compression value. Addresses #25945.

  5. 12.14.0

    Security fix7 Jun 20231 fix
7 other lines we could not sort, mostly version bumps
  • Cypress Cloud users can now receive desktop notifications about their runs, including when one starts, finishes, or fails. Addresses #26686.

    12.17.0
  • Cypress can now test pages with targeted Content-Security-Policy and Content-Security-Policy-Report-Only header directives by specifying the allow list via the experimentalCspAllowListconfiguration option. Addresses #1030. Addressed in #26483.

    12.15.0
  • The videoCompressionconfiguration option now accepts both a boolean or a Constant Rate Factor (CRF) number between 1 and 51. The videoCompression default value is still 32 CRF and when videoCompression is set to true the default of 32 CRF is used. Addresses #26658.

    12.15.0
  • The Cypress Cloud data shown on the Specs page and Runs page now reflect Cloud Runs that match the current Git tree if Git is being used. Addresses #26693.

    12.15.0
  • Removed @cypress/mocha-teamcity-reporteras this package was no longer being referenced. Addressed in #26938.

    12.15.0
  • A new testing type switcher has been added to the Spec Explorer to make it easier to move between E2E and Component Testing. An informational overview of each type is displayed if it hasn't already been configured to help educate and onboard new users to each testing type. Addresses #26448, #26836, and #26837.

    12.14.0
  • Ensures Git-related messages on the Runs page remain dismissed. Addresses #26808.

    12.14.0

1 internal line (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.