Update dependency mocha to v10.7.3 - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
mocha (source)	10.7.0 -> 10.7.3

---

Release Notes

mochajs/mocha (mocha)

v10.7.3

Compare Source

🩹 Fixes

• make release-please build work (#​5194) (afd66ef)

---

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, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[qodo-merge-pro]

CI Failure Feedback 🧐

(Checks updated until commit 9a6627b)

Action: Format / Check format script run

Failed stage: Run Bazel [❌]

Failure summary: The action failed due to an error in the Bazel build process: An error occurred during the fetch of the repository aspect_rules_jsnpm~npm. The error message indicates that the pnpm-lock.yaml file was updated, and suggests running the build again. The failure is related to the package @@aspect_rules_jsnpm~npm// not being found, which is likely due to the updated lock file. The build did not complete successfully, resulting in an exit code 1.

Relevant error logs: 1: ##[group]Operating System 2: Ubuntu ... 970: Package 'php-symfony-debug-bundle' is not installed, so not removed 971: Package 'php-symfony-dependency-injection' is not installed, so not removed 972: Package 'php-symfony-deprecation-contracts' is not installed, so not removed 973: Package 'php-symfony-discord-notifier' is not installed, so not removed 974: Package 'php-symfony-doctrine-bridge' is not installed, so not removed 975: Package 'php-symfony-doctrine-messenger' is not installed, so not removed 976: Package 'php-symfony-dom-crawler' is not installed, so not removed 977: Package 'php-symfony-dotenv' is not installed, so not removed 978: Package 'php-symfony-error-handler' is not installed, so not removed ... 1797: �[32mLoading:�[0m 0 packages loaded 1798: currently loading: 1799: �[32mLoading:�[0m 0 packages loaded 1800: currently loading: 1801: �[32mINFO: �[0mRepository aspect_rules_js~~npm~npm instantiated at: 1802: <builtin>: in <toplevel> 1803: Repository rule npm_translate_lock_rule defined at: 1804: /home/runner/.bazel/external/aspect_rules_js~/npm/private/npm_translate_lock.bzl:146:42: in <toplevel> 1805: �[31m�[1mERROR: �[0mAn error occurred during the fetch of repository 'aspect_rules_js~~npm~npm': 1806: Traceback (most recent call last): 1807: File "/home/runner/.bazel/external/aspect_rules_js~/npm/private/npm_translate_lock.bzl", line 112, column 21, in _npm_translate_lock_impl 1808: fail(msg) 1809: Error in fail: 1810: INFO: pnpm-lock.yaml file updated. Please run your build again. 1811: See https://github.com/aspect-build/rules_js/issues/1445 1812: �[32mLoading:�[0m 0 packages loaded 1813: currently loading: 1814: �[35mWARNING: �[0mTarget pattern parsing failed. 1815: �[31m�[1mERROR: �[0mSkipping '//:buildifier': no such package '@@aspect_rules_js~~npm~npm//': 1816: INFO: pnpm-lock.yaml file updated. Please run your build again. 1817: See https://github.com/aspect-build/rules_js/issues/1445 1818: �[31m�[1mERROR: �[0mno such package '@@aspect_rules_js~~npm~npm//': 1819: INFO: pnpm-lock.yaml file updated. Please run your build again. 1820: See https://github.com/aspect-build/rules_js/issues/1445 1821: �[32mINFO: �[0mElapsed time: 19.614s 1822: �[32mINFO: �[0m0 processes. 1823: �[31m�[1mERROR: �[0mBuild did NOT complete successfully 1824: �[31m�[1mERROR: �[0mBuild failed. Not running target 1825: �[0m 1826: ##[error]Process completed with exit code 1.

---

✨ CI feedback usage guide:

---

The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
The tool analyzes the failed checks and provides several feedbacks:

• Failed stage
• Failed test name
• Failure summary
• Relevant error logs

In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

/checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

Configuration options

• enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
• excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
• enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
• persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
• final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

See more information about the checks tool in the docs.