Skip to content

build(deps-dev): bump cypress from 4.2.0 to 4.4.0

Hannes Heine requested to merge pr3480head into pr3480base

Created by: Tirokk

dependabot-preview[bot] Authored by dependabot-preview[bot] Closed

Bumps cypress from 4.2.0 to 4.4.0.

Release notes

Sourced from cypress's releases.

4.4.0

Released 4/13/2020

Features:

  • TypeScript test files are now supported without using special preprocessors plugins. Addresses #1859.

Bugfixes:

  • We fixed an issue where Cypress could crash with a This socket has been ended by the other party error when testing applications that make use of WebSockets. Fixes #6458.
  • Uncaught errors thrown from within application or test code now display their proper stack trace. Fixes #6964.
  • Assertion errors now include a stack trace that includes the calling code. Fixes #6969.
  • We now clone the options object passed into Cypress commands so that they're not mutated and receive the proper options. Fixes #3171.
  • We fixed an issue where invalid Set-Cookie values could cause requests to fail with a cannot read property key of undefined error. Now, invalid Set-Cookie values will be ignored. Fixes #6890.

Misc:

  • Cypress no longer hides output from cypress --version, cypress version, cypress cache path, or cypress cache list commands when npm log level is silent or warn. Addresses #2705.
  • The cy.task() error message is now more specific about the promise resolution value required. Addresses #6241.

Dependency Updates:

  • Upgraded http-proxy from 1.17.0 to 1.18.0. Addressed in #6934.

4.3.0

Released 3/30/2020

Features:

  • Errors shown in the Test Runner have a new design including an expandable stack trace, better highlighting of code elements, and 'Learn more' links that link to relevant Cypress documentation. This is part of our larger improvements to error display with more exciting features to come. Addresses #3762.
  • When you open a Cypress project, clicking on the Settings tab and clicking into the Experiments panel will display the experimental features that are available and whether they are enabled for your project.
  • Added support for setting cookie sameSite values via cy.setCookie(). Addresses #2437.
  • Added experimental support for adding sameSite values to the objects yielded from cy.setCookie(), cy.getCookie(), and cy.getCookies(). Users can enable this by setting the experimentalGetCookiesSameSite configuration value to true. In Cypress 5, this will be the default. Addresses #2437.
  • Added support for the SameSite cookie attribute in cy.request(), cy.visit(), and proxied HTTP requests. Addresses #6757.
  • When an assertion is retried (using .should()) and fails, it now shows the diff in the stdout. Addresses #6722.

Bugfixes:

  • Fixed a regression in 4.2.0 where cypress installation could fail if Git is not installed. Fixes #6752.
  • Fixed a regression in 3.5.0 where certain HTTP requests could fail with Parse Error: Invalid header value char or Parse Error: Header overflow. Fixes #5602.
  • Fixed a regression in 4.2.0 where Electron deprecation warnings were printed to stderr in open mode. Fixes #6750.
  • Cookies set with a Domain containing an unknown TLD are now sent along for all requests. For example, a cookie like foo=bar; Domain=.cypress.test will now be sent during cy.request() to http://local.cypress.test. Fixes #6628.
  • We fixed a situation where a cross-origin errors could incorrectly throw in Chrome. Fixes #5270.
  • Visibility checks against vue-fragment elements no longer throw an unexpected error. Fixes #6745.
  • The stack trace is now properly shown in the console when clicking the command for tests having an .only that throw an error. Fixes #6744.
  • firefoxGcInterval can now correctly be set to null. Fixes #6825.
  • Cypress will no longer crash the process if an empty video chunk is received. Addressed in #6818.
  • Assertions failures on DOM elements no longer show unexpected diffs when they weren't retried. Fixes #6723.

Misc:

... (truncated)
Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

  • Update frequency (including time of day and day of week)
  • Pull request limits (per update run and/or open at any time)
  • Automerge options (never/patch/minor, and dev/runtime dependencies)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

Merge request reports