Packages

cypress

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

Upgrading cypress From 14.3.3 to 14.4.0

1 release in betweenevery note read

Reading releases, release notes and advisories…

Other targets from 14.3.3Newest 14.x14.5.4Latest16.3.0
  1. 14.3.3yours
  2. 14.4.0target
1
change to make
0
advisories fixed
0
new
2
fixes

Before you upgrade

Tick each one off as you go
  • Breaking14.4.0

Release by release

  1. 14.4.0

    Migration needed20 May 20252 fixes
    • Breaking

      Chrome 137+ no longer supports --load-extension in branded Chrome, breaking the @cypress/puppeteer plugin in open mode and headed run mode and launchOptions.extensions. We recommend using Electron, Chrome for Testing or Chromium to continue using these features. See Cypress Docker image examples for Chrome for Testing and Chromium. Addresses #31702 and #31703.

    • Fixed

      Fixed an issue where framebusting was occurring when top.window.location was being set explicitly. This fix does not require the experimentalModifyObstructiveThirdPartyCode configuration option. Addresses #31687.

    • Fixed

      Fixed an issue with the experimental usage of WebKit where Cypress incorrectly displayed 0 as the WebKit version. Addresses #31684.

6 other lines we could not sort, mostly version bumps
  • cy.press() now has a return type of Chainable<null> instead of void to match the convention of other commands that yield null. Addressed in #31698.

    14.4.0
  • Cursor is now available as an IDE option for opening files in Cypress, if it is installed on your system. Addressed in #31691.

    14.4.0
  • The error shown when the --record flag is missing has been updated to be shorter. Addressed in #31676.

    14.4.0
  • Upgraded @sinonjs/fake-timers from 8.1.0 to 10.3.0. Addressed in #31725 and #31737.

    14.4.0
  • Upgraded trash from 5.2.0 to 7.2.0. Addressed in #31667.

    14.4.0
  • Upgraded webdriver from 9.11.0 to 9.14.0. Addressed in #31689.

    14.4.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.