Packages

@cypress/schematic

6.0.0 · 26 Aug 2026MIT116k / weekRepositoryHomepagenpmAtom feed

Upgrading @cypress/schematic From 1.2.0 to 6.0.0

32 releases in betweennotes for 15

Reading releases, release notes and advisories…

Other targets from 1.2.0Newest 1.x1.7.0
  1. 1.2.0yours
  2. 10 releases
  3. 2.0.0major
  4. 10 releases
  5. 3.0.0major
  6. 4.0.0major
  7. 7 releases
  8. 5.0.0major
  9. 6.0.0target
10+
changes to make
0
advisories fixed
10+
new
21+
fixes

Counted from 15 of 32 release notes. Advisories are counted from the advisory database, in full.

Start here

Before you upgrade

Tick each one off as you go
  • Breaking5.0.0
  • Breaking5.0.0
  • Breaking5.0.0
  • Breaking4.0.0
  • Breaking4.0.0
  • Breaking3.0.0
  • Breaking2.0.0
  • Deprecated6.0.0
  • Deprecated6.0.0
  • Deprecated5.0.0

Release by release

  1. 6.0.0

    Deprecation26 Aug 20261 new · 1 fix
    • Deprecated

      The experimentalNetworkStubbing option has been removed and made the default behavior. You can safely removed this configuration option. Addressed in #9185.

    • Deprecated

      experimentalFetchPolyfill has been deprecated. We encourage you to use cy.intercept() to intercept requests using the Fetch API instead.

    • New

      Added the type of redirects and changed redirectedToUrl optional for Response types. Addresses #9275.

    • Fixed

      Fixed an issue where Content-Length for cy.route2 request bodies could be incorrectly recalculated. Fixes #9166.

  2. 5.0.0

    Migration needed19 Dec 2025
    • Breaking

      Cypress no longer supports file paths with a question mark ? in them. We now use the webpack preprocessor by default and it does not support files with question marks. Addressed in #7982.

    • Breaking

      Cypress now requires TypeScript 3.4+. Addressed in #7856.

    • Breaking

      Installing Cypress on your system now requires Node.js 10+. Addresses #6574.

    • Deprecated

      The cypress-plugin-retries plugin has been deprecated in favor of test retries built into Cypress. Addresses #1313.

  3. 4.3.0

    5 Dec 20252 new · 3 fixes
    • New

      Added support for setting cookie sameSite values via cy.setCookie(). Addresses #2437.

    • New

      Added support for the SameSite cookie attribute in cy.request(), cy.visit(), and proxied HTTP requests. Addresses #6757.

    • Fixed

      Fixed a regression in 4.2.0 where cypress installation could fail if Git is not installed. Fixes #6752.

    • Fixed

      Fixed a regression in 3.5.0 where certain HTTP requests could fail with Parse Error: Invalid header value char or Parse Error: Header overflow. Fixes #5602.

    • Fixed

      Fixed a regression in 4.2.0 where Electron deprecation warnings were printed to stderr in open mode. Fixes #6750.

  4. 4.1.1 – 4.2.05 releases, nothing new or fixed; 4 without a note

  5. 4.1.0

    14 Aug 20251 fix
    • Fixed

      Fixed a regression where Cypress could throw a "Maximum call stack size exceeded" error when transmitting a circular object over the internal WebSocket. Fixes #6582.

  6. 4.0.0

    Migration needed8 Aug 20253 new
  7. 3.0.0

    Migration needed8 Jan 20253 new · 4 fixes
    • Breaking

      screenshotOnHeadlessFailure has been removed as an option in cypress.json. Instead you can now control this behavior directly with code by setting screenshotOnRunFailure to false within the new Screenshot API. Fixes #1140 and #1754.

    • New

      Added Chrome flag --disable-blink-features=RootLayerScrolling to prevent the application under test from "shaking" in recent versions of Chrome. Fixes #1620.

    • New

      Added type definitions for Cypress.off and Cypress.log. Fixes #1110 and #1591.

    • New

      Added keywords to Cypress NPM package. Fixes #1508.

  8. 2.1.1 – 2.5.27 releases, no release note

230 other lines we could not sort, mostly version bumps
  • Cypress now always throws an error when asserting on an element that doesn't exist in the DOM (unless you're asserting that the element should not.exist). Assertions such as not.visible, not.contains, not.have.class, etc will now fail when used on non-existent DOM elements. Addresses #205.

    6.0.0
  • DOM elements where the CSS style (or ancestors) are opacity: 0 are no longer considered visible. However these are still considered actionable and "any action commands" interacting-with-elements#Actionability used to interact with the element will perform the action. This matches browser's implementation on how they regard elements with opacity: 0. Addresses #4474.

    6.0.0
  • The type yielded by cy.wait(alias) has changed in order to support use of cy.intercept(). Addressed in #9266.

    6.0.0
  • When using .type() and .click() on elements inside a contenteditable element, the events are now properly triggered on the inside elements. This may cause unintended consequences if you were relying on the previous behavior. Addressed in #9066.

    6.0.0
  • We removed several deprecation errors around APIs that were removed in versions of Cypress prior to 4.0.0. This will not cause any changes for anyone upgrading from a 4.0+ version of Cypress. For a full list of all APIs affected see #8946.

    6.0.0
  • We updated our HTTP status codes and reason phrases to match Node.js http.STATUS_CODES. If you have code that relies on a reason phrase, then this could affect you. Addressed in #8969.

    6.0.0
  • JSON request and response bodies captured by cy.intercept() are now automatically parsed, removing the need to manually do JSON.parse. Addressed in #9280.

    6.0.0
  • cy.route2() was renamed to cy.intercept(). We encourage you to update usages of cy.route2() to use cy.intercept(). Addressed in #9182.

    6.0.0
  • We now pass —disable-dev-shm-usage to the Chrome browser flags by default. This will write shared memory files into /tmp instead of /dev/shm. If you're passing this flag in your plugins file, you can now remove this code. Addresses #5336.

    6.0.0
  • A warning is now displayed when passing invalid configuration keys through the CLI. Addresses #428.

    6.0.0

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