Bump debug and @cypress/react in /web

[dependabot]

Bumps debug to 4.3.4 and updates ancestor dependency @cypress/react. These dependencies need to be updated together.

Updates debug from 4.1.1 to 4.3.4

Release notes

Sourced from debug's releases.

4.3.4

What's Changed

• Add section about configuring JS console to show debug messages by @​gitname in debug-js/debug#866
• Replace deprecated String.prototype.substr() by @​CommanderRoot in debug-js/debug#876

New Contributors

• @​gitname made their first contribution in debug-js/debug#866
• @​CommanderRoot made their first contribution in debug-js/debug#876

Full Changelog: debug-js/debug@4.3.3...4.3.4

4.3.3

Patch Release 4.3.3

This is a documentation-only release. Further, the repository was transferred. Please see notes below.

• Migrates repository from https://github.com/visionmedia/debug to https://github.com/debug-js/debug. Please see notes below as to why this change was made.
• Updates repository maintainership information
• Updates the copyright (no license terms change has been made)
• Removes accidental epizeuxis (#828)
• Adds README section regarding usage in child procs (#850)

Thank you to @​taylor1791 and @​kristofkalocsai for their contributions.

---

Repository Migration Information

I've formatted this as a FAQ, please feel free to open an issue for any additional question and I'll add the response here.

Q: What impact will this have on me?

In most cases, you shouldn't notice any change.

The only exception I can think of is if you pull code directly from https://github.com/visionmedia/debug, e.g. via a "debug": "visionmedia/debug"-type version entry in your package.json - in which case, you should still be fine due to the automatic redirection Github sets up, but you should also update any references as soon as possible.

Q: What are the security implications of this change?

If you pull code directly from the old URL, you should update the URL to https://github.com/debug-js/debug as soon as possible. The old organization has many approved owners and thus a new repository could (in theory) be created at the old URL, circumventing Github's automatic redirect that is in place now and serving malicious code. I (@​qix-) also wouldn't have access to that repository, so while I don't think it would happen, it's still something to consider.

Even in such a case, however, the officially released package on npm (debug) would not be affected. That package is still very much under control (even more than it used to be).

Q: What should I do if I encounter an issue related to the migration?

Search the issues first to see if someone has already reported it, and then open a new issue if someone has not.

Q: Why was this done as a 'patch' release? Isn't this breaking?

No, it shouldn't be breaking. The package on npm shouldn't be affected (aside from this patch release) and any references to the old repository should automatically redirect.

Thus, according to all of the "APIs" (loosely put) involved, nothing should have broken.

... (truncated)

Commits

• da66c86 4.3.4
• 9b33412 replace deprecated String.prototype.substr() (#876)
• c0805cc add section about configuring JS console to show debug messages (#866)
• 043d3cd 4.3.3
• 4079aae update license and more maintainership information
• 19b36c0 update repository location + maintainership information
• f851b00 adds README section regarding usage in child procs (#850)
• d177f2b Remove accidental epizeuxis
• e47f96d 4.3.2
• 1e9d38c cache enabled status per-logger (#799)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by qix, a new releaser for debug since your current version.

Updates @cypress/react from 5.12.4 to 8.0.1

Release notes

Sourced from @​cypress/react's releases.

8.0.0

Released 07/19/2021

Summary:

We've made some updates to ensure a consistent run experience across browsers. Now all browsers run via cypress run run headlessly, with a device pixel ratio of 1, and a screen size of 1280x720 by default.

Breaking Changes:

Please read our Migration Guide which explains the changes in more detail and how to change your code to migrate to Cypress 8.0.

• When running cypress run previous to 8.0, some browsers would launch headed while others were launched headless by default. Cypress now runs all browsers during cypress run as headless by default. Addresses #16832.
• The default screen size when running a headless browser has been reverted back to 1280x720 pixels (pre 7.0 behavior). Addresses #16853.
• When running the --headless Chrome browser via cypress run, the device pixel ratio will now be 1 by default, matching the behavior of all other browsers. This behavior can be overridden through the browser launch API. Addresses #17375.
• Cypress now enforces version checks for browser launching and will error during cypress run and not allow opening the browser in cypress open when attempting to open unsupported browser versions. Cypress supports Chrome >= 64, Firefox >= 86, and Edge >= 79. Addressed in #17355.
• Arguments returned from a chained function will no longer incorrectly be of type jQuery and instead have an any type. Fixes #16669.
• The Cypress.ConfigOptions, Cypress.ResolvedConfigOptions and Cypress.RuntimeConfigOption types have been updated so that ConfigOptions match the JSON schema. Addressed in #17251.

Features:

• You can now configure certificate authority (CA) and client certificates to use within tests on a per-URL basis via a clientCertificates configuration option. See Client certificates for more detail.
• Setting the environment variable ELECTRON_RUN_AS_NODE now starts Cypress as a normal Node.js process rather than an Electron process. See Running headless tests without Xvfb for more details. Addresses

... (truncated)

Commits

• d1b59a4 chore: release @​cypress/react-v8.0.1
• 1396e96 fix: handle promises rejected with undefined gracefully (#29454)
• 707c841 chore: Update Chrome (beta) to 125.0.6422.26 (#29468)
• 1bb5a73 misc: More accessibility fixes (#29322)
• f629856 chore(ci): Fix potential github action smells (#29416)
• 0e3dfd1 fix: pass all chromium flags through to Electron (#29443)
• c16a3bd chore: Revert "breaking: the supported eslint version is 8 for @​cypress/eslin...
• 0bfaa9a chore: fix changelog to point to correct PR (#29456)
• ed4f88f docs: add contributor security user namespace instructions (#29458)
• 2f1855f docs: update contributor python 3.11 instructions (#29457)
• 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.

[dryrunsecurity]

Hi there 👋, @DryRunSecurity here, below is a summary of our analysis and findings.

DryRun Security	Status	Findings
Configured Codepaths Analyzer	✅	0 findings
Sensitive Files Analyzer	❕	2 findings
Authn/Authz Analyzer	✅	0 findings
AppSec Analyzer	✅	0 findings
Secrets Analyzer	✅	0 findings

Note

🟢 Risk threshold not exceeded.

Change Summary (click to expand)

The following is a summary of changes in this pull request made by me, your security buddy 🤖.
Note that this summary is auto-generated and not meant to be a definitive list of security issues
but rather a helpful summary from a security perspective.

Summary:

The provided code change appears to be an update to the @cypress/react dependency in the web/package.json file. The version is being updated from 5.12.4 to 8.0.1. From an application security perspective, this change is not particularly concerning, as the @cypress/react package is a development dependency, which means it is only used during the development and testing phases of the application, and not in the production environment.

Updating development dependencies is a common practice to keep the project up-to-date with the latest versions of the tools and libraries used. Newer versions often include bug fixes, security patches, and feature improvements, which can benefit the overall project. However, it's important to review the release notes and change logs of the updated dependency to ensure that there are no known security vulnerabilities or breaking changes that could impact the application. Additionally, it's a good practice to thoroughly test the application after such updates to ensure that the changes do not introduce any unintended issues.

Files Changed:

• web/package.json: This file has been updated to change the version of the @cypress/react dependency from 5.12.4 to 8.0.1.

Powered by DryRun Security