This repository was archived by the owner on Mar 5, 2022. It is now read-only.
Update dependency @percy/cypress to v2 #192
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
|
🎉 This issue has been resolved in version 4.2.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.0.9->2.3.1Release Notes
percy/percy-cypress
v2.3.1Compare Source
Bug Fixes
v2.3.0Compare Source
Features
v2.2.0Compare Source
Features
2.1.1 (2019-09-20)
Bug Fixes
percyCSSoption to types (#156) (7475783)v2.1.1Compare Source
Bug Fixes
percyCSSoption to types (#156) (7475783)v2.1.0Compare Source
Features
2.0.1 (2019-08-26)
Bug Fixes
v2.0.1Compare Source
Bug Fixes
v2.0.0Compare Source
Bug Fixes
cy.taskfor health check rather thancy.exec(BREAKING CHANGE) (#140) (40550f7), closes #104 #104 #138BREAKING CHANGES
The problem
In all of the Percy SDKs we do a thing called a "heath check", which makes sure the Percy agent server is open and ready to accept the DOM we're going to
POSTto it. If the health check fails, we will disable Percy in the SDK so we're not failing your tests due to Percy not running.In the Cypress SDK, this was implemented in an interesting way due a limitation with
cy.request. The TL:DR of that is we can't.catcha failed request, so we needed to usecy.execto health check & gracefully fall out. You can read a little more about that limitation here: cypress-io/cypress#31611.0.9 (2019-05-08)
Bug Fixes
1.0.8 (2019-05-02)
Bug Fixes
1.0.7 (2019-04-30)
Bug Fixes
@percy/agentversion range (tilde over caret) (#92) (0e4b3f9), closes /github.com/npm/node-semver#caret-ranges-123-025-004 /github.com/npm/node-semver#tilde-ranges-123-12-11.0.6 (2019-04-09)
Bug Fixes
Renovate configuration
📅 Schedule: "every weekend" in timezone America/New_York.
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻️ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by WhiteSource Renovate. View repository job log here.