Skip to content
This repository has been archived by the owner on Sep 4, 2024. It is now read-only.

chore(deps): bump tough-cookie and testcafe #579

Merged

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Sep 10, 2023

Bumps tough-cookie to 4.1.3 and updates ancestor dependency testcafe. These dependencies need to be updated together.

Updates tough-cookie from 4.0.0 to 4.1.3

Release notes

Sourced from tough-cookie's releases.

4.1.3

Security fix for Prototype Pollution discovery in #282. This is a minor release, although output from the inspect utility is affected by this change, we felt this change was important enough to be pushed into the next patch.

4.1.2 -- Patch and Bugfix Release

What's Changed

Full Changelog: salesforce/tough-cookie@v4.1.1...v4.1.2

4.1.1

Patch Release

What's Changed

Full Changelog: salesforce/tough-cookie@v4.1.0...v4.1.1

4.1.0

v4.1.0

Minor release, focused mainly on resolving reported issues and some minor feature work.

What's Changed

... (truncated)

Commits
  • 4ff4d29 4.1.3 release preparation, update the package and lib/version to 4.1.3. (#284)
  • 12d4747 Prevent prototype pollution in cookie memstore (#283)
  • f06b72d Fix documentation for store.findCookies, missing allowSpecialUseDomain proper...
  • b1a8898 fix: allow set cookies with localhost (#253)
  • ec70796 4.1.1 Patch -- allow special use domains by default (#250)
  • d4ac580 fix: allow special use domains by default (#249)
  • 79c2f7d 4.1.0 release to NPM (#245)
  • 4fafc17 Prepare tough-cookie 4.1 for publishing (updated GitHub actions, move Dockerf...
  • aa4396d fix: distinguish between no samesite and samesite=none (#240)
  • b8d7511 Modernize README (#234)
  • Additional commits viewable in compare view

Updates testcafe from 2.6.2 to 3.3.0

Release notes

Sourced from testcafe's releases.

v3.3.0 (2023-08-29)

TestCafe v3.3.0 includes important bug fixes and quality of life improvements.

Bug Fixes

  • TestCafe terminates the test run when it attempts to parse an empty JSON file (#7935).
  • Firefox throws an unexpected error when TestCafe attempts to close the browser window (#7285).
  • [Native Automation] TestCafe ignores the --disable-multiple-windows option when you interact with a link that points to "target=_blank", or open a new window with the window.open method (#7916).
  • [Native Automation] TestCafe ignores the clientScripts directive when you mock HTTP requests (#7914).
  • [Native Automation] TestCafe hangs when it runs tests in the headless version of Google Chrome (#7898).
  • [Native Automation] TestCafe doesn't throw an error when the user attempts to enable the userProfile option (#7925).

v3.3.0-rc.2

What’s Changed

v3.3.0-rc.1

What’s Changed

v3.2.0

TestCafe v3.2.0 Released

TestCafe v3.2.0 allows you to check whether TestCafe uses native automation to control the browser.

Check your native automation status

The nativeAutomation property of the t.browser object indicates whether TestCafe uses native automation to control the browser. The property's value is true when TestCafe uses native automation and false when TestCafe uses the Hammerhead proxy.

... (truncated)

Changelog

Sourced from testcafe's changelog.

v3.3.0 (2023-08-29)

TestCafe v3.3.0 includes important bug fixes and quality of life improvements.

Bug Fixes

  • TestCafe terminates the test run when it attempts to parse an empty JSON file (#7935).
  • Firefox throws an unexpected error when TestCafe attempts to close the browser window (#7285).
  • [Native Automation] TestCafe ignores the --disable-multiple-windows option when you interact with a link that points to "target=_blank", or open a new window with the window.open method (#7916).
  • [Native Automation] TestCafe ignores the clientScripts directive when you mock HTTP requests (#7914).
  • [Native Automation] TestCafe hangs when it runs tests in the headless version of Google Chrome (#7898).
  • [Native Automation] TestCafe doesn't throw an error when the user attempts to enable the userProfile option (#7925).

v3.2.0 (2023-08-17)

TestCafe v3.2.0 allows you to check whether TestCafe uses native automation to control the browser.

Check your native automation status

The nativeAutomation property of the t.browser object indicates whether TestCafe uses native automation to control the browser. The property's value is true when TestCafe uses native automation and false when TestCafe uses the Hammerhead proxy.

You can check the browser's native automation status before you start the test:

import { Selector } from 'testcafe';
fixtureTestController.browser
.pagehttps://example.com;
test('Native automation check', async t => {
await t.expect(t.browser.nativeAutomation).ok();
//the test continues only if you use native automation
});

Bug Fixes

  • TestCafe uses a version of the error-stack-parser package that contains a vulnerable dependency ([PR #7919](DevExpress/testcafe#7919) by @​sethidden).
  • TestCafe does not clear cookie storage if a Role activation URL is the same as the page URL (#7874).
  • [Native Automation] TestCafe incorrectly processes web pages with file inputs (#7886).

v3.1.0 (2023-07-27)

TestCafe v3.1.0 introduces two enhancements:

  • You can now respond to geolocation requests with the t.setNativeDialogHandler method.
  • Your tests and test reports can now reference a variable that stores the framework's version number.

Respond to geolocation requests

... (truncated)

Commits
  • c4493a0 release: updated version (#7980)
  • 4d3ef63 release: fix package-lock (#7975)
  • b8f13ac release: updated version (#7974)
  • a6a0cd7 fix error message for :userProfile (#7972)
  • d26cb24 publish: v3.3.0-rc.1 (#7961)
  • ed16cb4 Browsers with "userProfile" option in Native Automation (closes #7925) (#7958)
  • 0bdd78a refactor: removed IE leftovers from test\client (#7964)
  • 5c58735 refactor: removed IE and MS Edge Legacy leftovers from test\client\fixtures (...
  • 6424187 build(deps): bump flat, gulp-mocha-simple and mocha-reporter-spec-with-retrie...
  • 346caf6 refactor: removed IE and MS Edge Legacy leftovers from test\client\legacy-fix...
  • Additional commits viewable in compare view

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @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)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

Bumps [tough-cookie](https://github.com/salesforce/tough-cookie) to 4.1.3 and updates ancestor dependency [testcafe](https://github.com/DevExpress/testcafe). These dependencies need to be updated together.


Updates `tough-cookie` from 4.0.0 to 4.1.3
- [Release notes](https://github.com/salesforce/tough-cookie/releases)
- [Changelog](https://github.com/salesforce/tough-cookie/blob/master/CHANGELOG.md)
- [Commits](salesforce/tough-cookie@v4.0.0...v4.1.3)

Updates `testcafe` from 2.6.2 to 3.3.0
- [Release notes](https://github.com/DevExpress/testcafe/releases)
- [Changelog](https://github.com/DevExpress/testcafe/blob/master/CHANGELOG.md)
- [Commits](DevExpress/testcafe@v2.6.2...v3.3.0)

---
updated-dependencies:
- dependency-name: tough-cookie
  dependency-type: indirect
- dependency-name: testcafe
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies 📦 Pull requests that update a dependency file label Sep 10, 2023
@probil probil merged commit 05868b5 into master Sep 10, 2023
@probil probil deleted the dependabot/npm_and_yarn/tough-cookie-and-testcafe-4.1.3 branch September 10, 2023 21:19
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
dependencies 📦 Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant