# Cypress v2.0.0 — Release & Upgrade Intelligence
- **Product:** Cypress (https://www.cypress.io)
- **Version:** v2.0.0
- **Released:** Jul 19, 2018
- **Impact Score:** 7/10
- **Breaking Changes:** Source flagged
- **Canonical Analysis:** https://changelogs.us/cypress/updates/v2.0.0/

## Executive Summary (TL;DR)
Cypress v2.0.0. Source highlight: *Released 2/15/2018*

## Breaking Changes & Deprecations
- Breaking Changes:** - The built in default `Electron` browser has been bumped from version `53` to `59`. This version represents the version of `Chromium` that Electron is using. In other words, running `cypress run` (or via `Electron`) will be like running your tests in `Chrome 59` now. Although it is unlikely this would actually *break* any of your tests - it is technically possible they could behave differently. Fixes [#895](https://github.com/cypress-io/cypress/issues/895) and [#891](https://github.com/cypress-io/cypress/issues/891) and [#823](https://github.com/cypress-io/cypress/issues/8

## Bug Fixes
- The built in default `Electron` browser has been bumped from version `53` to `59`. This version represents the version of `Chromium` that Electron is using. In other words, running `cypress run` (or via `Electron`) will be like running your tests in `Chrome 59` now. Although it is unlikely this would actually *break* any of your tests - it is technically possible they could behave differently. Fixes #895 and #891 and #823 and #860 and #1011 and #1252 and #1276.
- We are now detecting and automatically stripping code that obstructs Cypress from being able to test your application. Specifically, we are removing JavaScript code that tries to prevent **clickjacking** and **framebusting**. We have written very conservative rules that do their best to **only** strip these specific JS snippets, but it is technically possible that it may unintentionally rewrite valid JS if they match the regexp patterns. There is a new configuration option called `modifyObstruct
- We are now clearing the browser's disk cache each time it opens (before any tests run). This means that any files that have been cached from `Cache-Control` headers will be cleaned and removed. In the future, we will expose a new `cy.clearCache()` method to provide finer grained control of clearing the cache on a per test basis. But for now, this is an improvement. Fixes #1124.
- The `--spec` option is now normalized against the current working directory `cwd` instead of the project that you are running Cypress in. That means passing a path from the command line to a spec file will now work even when the project path is not `cwd`. Fixes #1159.
- `blacklistHosts` would occasionally not work if you were blacklisting a host that had previously cached a file. In this case, the browser would serve it from disk and not make an actual HTTP request. This issue has been solved by clearing the cache when the browser opens. Fixes #1154.
- Spies and Stubs created with `cy.stub()` and `cy.spy()` will now retry their assertions when utilized from an alias. Fixes #1156.