react-router-navigation-prompt
react-router-navigation-prompt copied to clipboard
build(deps): bump jsonwebtoken and testcafe
Bumps jsonwebtoken to 9.0.0 and updates ancestor dependency testcafe. These dependencies need to be updated together.
Updates jsonwebtoken from 8.5.1 to 9.0.0
Changelog
Sourced from jsonwebtoken's changelog.
9.0.0 - 2022-12-21
Breaking changes: See Migration from v8 to v9
Breaking changes
- Removed support for Node versions 11 and below.
- The verify() function no longer accepts unsigned tokens by default. ([834503079514b72264fd13023a3b8d648afd6a16]https://github.com/auth0/node-jsonwebtoken/commit/834503079514b72264fd13023a3b8d648afd6a16)
- RSA key size must be 2048 bits or greater. ([ecdf6cc6073ea13a7e71df5fad043550f08d0fa6]https://github.com/auth0/node-jsonwebtoken/commit/ecdf6cc6073ea13a7e71df5fad043550f08d0fa6)
- Key types must be valid for the signing / verification algorithm
Security fixes
- security: fixes
Arbitrary File Write via verify function- CVE-2022-23529- security: fixes
Insecure default algorithm in jwt.verify() could lead to signature validation bypass- CVE-2022-23540- security: fixes
Insecure implementation of key retrieval function could lead to Forgeable Public/Private Tokens from RSA to HMAC- CVE-2022-23541- security: fixes
Unrestricted key type could lead to legacy keys usage- CVE-2022-23539
Commits
e1fa9dcMerge pull request from GHSA-8cf7-32gw-wr335eaedbfchore(ci): remove github test actions job (#861)cd4163echore(ci): configure Github Actions jobs for Tests & Security Scanning (#856)ecdf6ccfix!: Prevent accidental use of insecure key sizes & misconfiguration of secr...8345030fix(sign&verify)!: Remove defaultnonesupport fromsignandverifymet...7e6a86bUpload OpsLevel YAML (#849)74d5719docs: update references vercel/ms references (#770)d71e383docs: document "invalid token" error3765003docs: fix spelling in README.md: Peak -> Peek (#754)a46097edocs: make decode impossible to discover before verify- Additional commits viewable in compare view
Maintainer changes
This version was pushed to npm by julien.wollscheid, a new releaser for jsonwebtoken since your current version.
Updates testcafe from 1.18.3 to 2.2.0
Release notes
Sourced from testcafe's releases.
v2.2.0 (2022-12-29)
TestCafe v2.2.0 introduces user-defined custom actions and an important experimental capability. Google Chrome users can now enable "proxyless mode" to speed up their test suite.
Custom Action Support
TestCafe users can now define custom test actions. Place the definition function in a JavaScript configuration file:
module.exports = { customActions: { async makeCoffee (args) { await this.click(args); }, } };Include custom methods in your tests alongside other TestController methods. Add the
customActionsprefix when you call the action:test('Test with a custom action', async t => { await t.click() .customActions.makeCoffee() .click(); })Experimental: Proxyless mode
TestCafe runs an under-the-hood reverse proxy to automate tests across different browsers. But this technique complicates the framework. Native automation protocols offer superior automation speeds and greater stability. That's why the TestCafe team decided to gradually phase the reverse proxy out in favor of native support for these automation protocols.
TestCafe v2.2.0 includes an experimental option that disables the proxy for Google Chrome.
testcafe chrome tests --experimental-proxylessYou can enable this option in the command line interface, the Test Runner API, and the configuration file. Read the Proxyless mode guide for more information.
Bug Fixes
- TestCafe doesn't hide the live mode status bar when the bar obstructs the action target (#7384)
- The 'Target element is overlapped' message does not reference the Selector that caused the warning (#7386)
- The TestCafe Dashboard reporter includes an outdated
uuiddependency (testcafe-reporter-dashboard#111)- TestCafe doesn't display the correct error message when the framework throws an exception (#6936)
- TestCafe retains some cookies after the user requests their deletion (PR testcafe-hammerhead#2818)
- TestCafe cannot load test pages with the
localhostURL on Node.js v17 and up (#7396)- TestCafe cannot take screenshots in headless Chrome on Node.js v17 and up (#7408)
... (truncated)
Changelog
Sourced from testcafe's changelog.
v2.2.0 (2022-12-29)
TestCafe v2.2.0 introduces user-defined custom actions and an important experimental capability. Google Chrome users can now enable "proxyless mode" to speed up their test suite.
Custom Action Support
TestCafe users can now define custom test actions. Place the definition function in a JavaScript configuration file:
module.exports = { customActions: { async makeCoffee (args) { await this.click(args); }, } };Include custom methods in your tests alongside other TestController methods. Add the
customActionsprefix when you call the action:test('Test with a custom action', async t => { await t.click() .customActions.makeCoffee() .click(); })Experimental: Proxyless mode
TestCafe runs an under-the-hood reverse proxy to automate tests across different browsers. But this technique complicates the framework. Native automation protocols offer superior automation speeds and greater stability. That's why the TestCafe team decided to gradually phase the reverse proxy out in favor of native support for these automation protocols.
TestCafe v2.2.0 includes an experimental option that disables the proxy for Google Chrome.
testcafe chrome tests --experimental-proxylessYou can enable this option in the command line interface, the Test Runner API, and the configuration file. Read the Proxyless mode guide for more information.
Bug Fixes
- TestCafe doesn't hide the live mode status bar when the bar obstructs the action target (#7384)
- The 'Target element is overlapped' message does not reference the Selector that caused the warning (#7386)
- The TestCafe Dashboard reporter includes an outdated
uuiddependency (testcafe-reporter-dashboard#111)- TestCafe doesn't display the correct error message when the framework throws an exception (#6936)
- TestCafe retains some cookies after the user requests their deletion (PR testcafe-hammerhead#2818)
- TestCafe cannot load test pages with the
localhostURL on Node.js v17 and up (#7396)- TestCafe cannot take screenshots in headless Chrome on Node.js v17 and up (#7408)
... (truncated)
Commits
319e764release: publish v2.2.0 (#7444)6fb1727add types for TestController.customActions property (#7440)770f1a1release: update the TestCafe Dashboard reporter, publish v2.2.0-rc.2 (#7427)bc95932release: publish v2.2.0-rc.1d0d0a28release: publish v2.2.0-rc.1d95ec85release: publish 2.1.1-alpha.3 (#7420)f3dc5d2Introduce CustomActions feature (closes #1535) (#7393)5534e34proxyless: fix 'window.postMessage' function (#7414)aed7683ci: remove duplicated workflow [skip ci]a5b5568ci: remove duplicated workflow [skip ci]- 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill 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 versionwill 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 dependencywill 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.