chore(deps): update dependency cypress to v10

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
cypress	9.6.0 -> 10.1.0

---

Release Notes

cypress-io/cypress

v10.1.0

Compare Source

Changelog: https://docs.cypress.io/guides/references/changelog#​10-1-0

v10.0.3

Compare Source

Changelog: https://docs.cypress.io/guides/references/changelog#​10-0-3

v10.0.2

Compare Source

Changelog: https://docs.cypress.io/guides/references/changelog#​10-0-2

v10.0.1

Compare Source

Changelog: https://docs.cypress.io/guides/references/changelog#​10-0-1

v10.0.0

Compare Source

Changelog: https://docs.cypress.io/guides/references/changelog#​10-0-0

v9.7.0

Compare Source

Released 5/23/2022

Features:

• The Electron version and shipped Chromium browser version has been updated.
  Addressed in #​21418.

Deprecations:

• The Cypress.Cookies.preserveOnce() and Cypress.Cookies.defaults() Cypress
  APIs have been deprecated. In a future release, support for
  Cypress.Cookies.preserveOnce() and Cypress.Cookies.defaults() will be
  removed. Consider using the experimental
  cy.session() command instead to cache and restore
  cookies and other sessions details between tests. Fixed
  #​21333.

Bugfixes:

• Updated the cy.contains() command to correctly
  error and retry if the provided regex pattern begins with an equal sign and a
  match was not initially found. Previously the command would incorrectly fail
  with a syntax error. Fixed
  #​21108.
• Corrected the cy.session() command log grouping and validation verbiage.
  This change provides better insights to logs associated with the command.
  Fixed #​21377.
• Removed eventemitter2 third-party type definitions from cy and Cypress
  that were unintentionally exposed. Fixed
  #​20556.

Dependency Updates:

• Upgraded the bundled node version shipped with Cypress from 16.5.0 to
  16.13.2. Addressed in
  #​21418.
• Upgraded the Chromium browser version used during cypress run and when
  selecting Electron browser in cypress open from 94.0.4606.81 to
  100.0.4896.75. Addressed in
  #​21418.
• Upgraded electron dependency from 15.5.1 to 18.0.4. Addressed in
  #​21418.

v9.6.1

Compare Source

Released 5/9/2022

Bugfixes:

• Cypress can now launch on systems where Firefox is installed via Snapcraft.
  Fixed #​19793.
• Updates were made to ensure XHR calls are properly displaying the response
  body in the command log. Fixed
  #​21361.
• Fixed cy.contains() and
  .should('contain', ...) to handle finding text that
  contains backslash characters. Fixed
  #​19116
• Updated .type('{enter}') to support sending the Enter
  keystroke to submit buttons that are not rendered within a form html element,
  but are associated with a form via the form attribute. Fixed
  #​21163.
• Fixed an issue with cy.session() such that re-running tests in open mode
  will now correctly recreate a session. Before this change, an error was thrown
  indicating the saved setup function was not a function because it was
  serialized. Fixed
  #​17805.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 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.

---

• If you want to rebase/retry this PR, click this checkbox.

---

This PR has been generated by Mend Renovate. View repository job log here.

[netlify]

✅ Deploy Preview for redwoodblog-dev ready!

Name	Link
🔨 Latest commit	65a60c1
🔍 Latest deploy log	https://app.netlify.com/sites/redwoodblog-dev/deploys/62ad1e48a850a200094ba089
😎 Deploy Preview	https://deploy-preview-50--redwoodblog-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[pull-request-quantifier-deprecated]

This PR has 2 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Extra Small
Size       : +1 -1
Percentile : 0.8%

Total files changed: 2

Change summary by file extension:
.json : +1 -1
.lock : +0 -0

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detetcted.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication