Impact Score: 5/10
Cypress: 0.13.2
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.13.2. Source highlight: *Released 12/20/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.
✨ New Features & Capabilities (2)
- Added `responseTimeout` configuration value.
- Added special error messages when elements can not have actions applied to them with a suggestion to use `{force: true}`.
🔧 Bug Fixes & Patches (1)
- Added cache buster to test files which forces them to be reloaded in the `Sources` panel after making modifications. In previous versions when test files were live reloaded Chrome would not display their new contents due to a bug in Dev Tools. We've now worked around this issue.
📄 View Raw Release Notes (Original Developer Log)
*Released 12/20/2015*
**Notes:**
- Docs have been updated for [cy.wait()](https://on.cypress.io/wait), [cy.route()](https://on.cypress.io/route) and [cy.server()](https://on.cypress.io/server) to reflect these changes.
**Features:**
- Added `responseTimeout` [configuration](https://on.cypress.io/configuration) value.
- [cy.wait()](https://on.cypress.io/wait) has been upgraded to now use two separate `timeout` values. In previous versions [cy.wait()](https://on.cypress.io/wait) used the `commandTimeout` and would automatically time out if the XHR did not achieve a response in that time frame. Now [cy.wait()](https://on.cypress.io/wait) will go through two independent timeout phases. At first [cy.wait()](https://on.cypress.io/wait) will wait for an XHR to be requested which matches its route. It will wait up to the value configured with `requestTimeout` (default 5000ms). After it sees a matching request it will then go into `response` waiting mode. It will wait up to the value configured with `responseTimeout` (default 20000ms). When [cy.wait()](https://on.cypress.io/wait) fails you now receive a much better error message indicating exactly which phase failed. Whether a request was never sent out, or whether it timed out waiting for a response. This gives you the best of both worlds and prevents situations where Cypress was timing out on slow servers. By creating new configuration values: `requestTimeout` and `responseTimeout` you can now directly control this behavior without affecting other regular commands.
**Bugfixes:**
- Prevent removing trailing new lines on fixtures after formatting.
- Added cache buster to test files which forces them to be reloaded in the `Sources` panel after making modifications. In previous versions when test files were live reloaded Chrome would not display their new contents due to a bug in Dev Tools. We've now worked around this issue.
**Misc:**
- Removed `{stub: false}` option from [cy.server()](https://on.cypress.io/server) and [cy.route()](https://on.cypress.io/route). Cypress will now log a deprecation warning when you use the this option. Removing this option helps simplify the API because now Cypress can figure out whether you really want to stub the route based on whether you've provided a response or not. If you have not provided a response, the default behavior will be to not stub. If you do provide a response, Cypress will stub the route.
- Repurposed `requestTimeout` to now mean the time we wait for an XHR to be requested. Changed [cy.request()](https://on.cypress.io/request) to now use `responseTimeout` configuration value.
- Updated many error messages to be more consistent.
- Added special error messages when elements can not have actions applied to them with a suggestion to use `{force: true}`.