cypress
16.3.0 · 10 Nov 2026MIT7.6M / weekRepositoryHomepagenpmAtom feed
Upgrading cypress From 16.0.0 to 16.1.0
1 release in betweenevery note read
Reading releases, release notes and advisories…
Release by release
- 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
2 other lines we could not sort, mostly version bumps
- 16.1.0
cypress tap runnow reports that the spec is running and to usecypress tap statusfor progress, instead of printing the launched spec's testing type and browser. #34777. - 16.1.0
When a Test Replay recording fails while being prepared for a spec during
cypress run, Cypress now recommends increasing available disk space and confirming that the temporary directory used for Test Replay recordings is readable and writable, instead of printing only the underlying error such asSqliteError: unable to open database file. Addressed in #34763.
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.