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

Cypress: 0.12.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.

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

Cypress v0.12.2. Source highlight: *Released 11/01/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 (1)

  • `Environment Variable` support has been added and can be accessed in your tests with Cypress.env. The docs have been written Environment Variable and here.

๐Ÿ”ง Bug Fixes & Patches (1)

  • The `URL` property on all XHR's is now completely decoded, even on URL's which were originally encoded. The reason is for easier assertions and debugging. This `URL` property is specific to Cypress and does not actually affect the underlying XHR.
๐Ÿ“„ View Raw Release Notes (Original Developer Log)
*Released 11/01/2015* **Features:** - There is now a `cy.cmd` and `cy.command` method which enables you to invoke commands by their string name. This is most useful when using *namespaced* custom commands. So `Cypress.addParentCommand("dashboard.setSlider", ...)` can be accessed by `cy.cmd("dashboard.setSlider", arg1, arg2)`. (Docs have not been written yet). - `Environment Variable` support has been added and can be accessed in your tests with [Cypress.env](https://on.cypress.io/env). The docs have been written [Environment Variable](https://on.cypress.io/environment-variables) and [here](https://on.cypress.io/env). **Misc:** - The `URL` property on all XHR's is now completely decoded, even on URL's which were originally encoded. The reason is for easier assertions and debugging. This `URL` property is specific to Cypress and does not actually affect the underlying XHR.