Cypress v0.11.3stable Released Jul 19, 2018
Impact Score: 5/10

Cypress: 0.11.3

Source available โ€” automated, not human-reviewed

Component: cypress ยท Channel: stable. Automated analysis, not a compatibility certification. How this works.

Analysis updated: 2026-11-01.

Compatibility not verified โ€” check source notes
๐Ÿ“„ .MD
โšก Executive Summary (TL;DR)

Cypress v0.11.3. Source highlight: *Released 09/16/2015*

Who Does This Impact? (Role-Based Analysis)

๐Ÿ’ป Software Engineers & Devs

Check the source notes against the package and APIs you use before upgrading.

๐Ÿ“Š Product & Engineering Leads

Use the documented changes to assess relevance to your product; release frequency alone is not a quality measure.

โš™๏ธ DevOps & Security

Verify the target version, runtime requirements and rollback procedure in the official documentation.

๐Ÿ”ง Bug Fixes & Patches (2)

  • XHR's will no longer be ended early and display no status as if there was no response. Fixes #63.
  • XHR's which are aborted no longer cause an `INVALID_STATE_ERR` to be thrown. Fixes #62 and #34.
๐Ÿ“„ View Raw Release Notes (Original Developer Log)
*Released 09/16/2015* **Features:** - When XHR's are aborted Cypress will display the stack trace indicating where in your app the XHR was aborted. Additionally it will display s `(aborted)` in the command log. **Bugfixes:** - XHR's will no longer be ended early and display no status as if there was no response. Fixes [#63](https://github.com/cypress-io/cypress/issues/63). - XHR's which are aborted no longer cause an `INVALID_STATE_ERR` to be thrown. Fixes [#62](https://github.com/cypress-io/cypress/issues/62) and [#34](https://github.com/cypress-io/cypress/issues/34). - Cypress will no longer incorrectly revert to a previous test run's snapshot when tests are re-run.