Impact Score: 5/10
Cypress: 0.17.9
Source available — automated, not human-reviewed
Component: cypress · Channel: stable. Automated analysis, not a compatibility certification. How this works.
Analysis updated: 2026-11-01.
⚡ Executive Summary (TL;DR)
Cypress v0.17.9. Source highlight: *Released 10/22/2016*
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 (3)
- Cypress now applies cookies to the browser which were cleared between redirects. Fixes #224.
- Snapshots now work even when `<html>` tag has invalid attributes. Fixes #271.
- Cypress no longer crashes on initial cy.visit() when the 3rd party web server never ends the response. Fixes #272.
📄 View Raw Release Notes (Original Developer Log)
*Released 10/22/2016*
**Bugfixes:**
- Cypress now applies cookies to the browser which were cleared between redirects. Fixes [#224](https://github.com/cypress-io/cypress/issues/224).
- Snapshots now work even when `<html>` tag has invalid attributes. Fixes [#271](https://github.com/cypress-io/cypress/issues/271).
- Cypress no longer crashes on initial [cy.visit()](https://on.cypress.io/visit) when the 3rd party web server never ends the response. Fixes [#272](https://github.com/cypress-io/cypress/issues/272).
**Misc:**
- Changed default [responseTimeout](https://on.cypress.io/configuration#Timeouts) from `20000` to `30000`.
- Changed default [pageLoadTimeout](https://on.cypress.io/configuration#Timeouts) from `30000` to `60000`.
- The internal Cypress proxy now forcibly responds to requests taking longer than `responseTimeout`. Currently this sends back `text/html` with the `ETIMEDOUT` error, but this likely needs to be configurable. The reason we are now forcibly applying timeouts is to prevent `socket pooling exhaustion` where tests are running and a 3rd party server never responds to the request.