chore(deps): update dependency mocha to v10.7.0 - abandoned

[renovate]

This PR contains the following updates:

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

---

Release Notes

mochajs/mocha (mocha)

v10.7.0

Compare Source

🎉 Enhancements

• #​4771 feat: add option to not fail on failing test suite (@​ilgonmic)

v10.6.1

Compare Source

🐛 Fixes

• #​3825 fix: do not exit when only unref'd timer is present in test code (@​boneskull)
• #​5040 fix: support canonical module (@​JacobLey)

---

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 has been generated by Mend Renovate. View repository job log here.

[netlify]

✅ Deploy Preview for selenium-dev ready!

Name	Link
🔨 Latest commit	d25736b
🔍 Latest deploy log	https://app.netlify.com/sites/selenium-dev/deploys/66a1ede00c27700008d98a38
😎 Deploy Preview	https://deploy-preview-1824--selenium-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 configuration.

[qodo-merge-pro]

CI Failure Feedback 🧐

(Checks updated until commit bfcc88d)

Action: tests (macos, nightly)

Failed stage: Run tests [❌]

Failure summary: The action failed because the npm test command encountered an error during its execution. Specifically: The npx mocha command failed with an error stating that every node program run under Bazel must have a $RUNFILES_DIR, $RUNFILES, or $RUNFILES_MANIFEST_FILE environment variable set. This error occurred during all three attempts to run the tests, resulting in the child process exiting with error code 1 each time.

Relevant error logs: 1: ##[group]Operating System 2: macOS ... 250: timeout_minutes: 20 251: max_attempts: 3 252: command: cd examples/javascript 253: npm test 254: 255: retry_wait_seconds: 10 256: polling_interval_seconds: 1 257: warning_on_retry: true 258: continue_on_error: false ... 263: CHROME_BIN: /Users/runner/hostedtoolcache/setup-chrome/chromium/stable/arm64/Contents/MacOS/chrome 264: EDGE_BIN: /Users/runner/hostedtoolcache/msedge/stable/x64/Contents/MacOS/Microsoft Edge 265: FF_BIN: /Users/runner/hostedtoolcache/firefox/latest/x64/Contents/MacOS/firefox 266: NPM_CONFIG_USERCONFIG: /Users/runner/work/_temp/.npmrc 267: NODE_AUTH_TOKEN: XXXXX-XXXXX-XXXXX-XXXXX 268: ##[endgroup] 269: > [email protected] test 270: > npx mocha test/**/*.spec.js --timeout 60000 271: Exception during run: Error: Every node program run under Bazel must have a $RUNFILES_DIR, $RUNFILES or $RUNFILES_MANIFEST_FILE environment variable ... 293: at ModuleJob.run (node:internal/modules/esm/module_job:195:25) 294: at async ModuleLoader.import (node:internal/modules/esm/loader:337:24) 295: at async importModuleDynamicallyWrapper (node:internal/vm/module:432:15) 296: at async formattedImport (/Users/runner/work/seleniumhq.github.io/seleniumhq.github.io/examples/javascript/node_modules/mocha/lib/nodejs/esm-utils.js:9:14) 297: at async exports.requireOrImport (/Users/runner/work/seleniumhq.github.io/seleniumhq.github.io/examples/javascript/node_modules/mocha/lib/nodejs/esm-utils.js:42:28) 298: at async exports.loadFilesAsync (/Users/runner/work/seleniumhq.github.io/seleniumhq.github.io/examples/javascript/node_modules/mocha/lib/nodejs/esm-utils.js:100:20) 299: at async singleRun (/Users/runner/work/seleniumhq.github.io/seleniumhq.github.io/examples/javascript/node_modules/mocha/lib/cli/run-helpers.js:162:3) 300: at async exports.handler (/Users/runner/work/seleniumhq.github.io/seleniumhq.github.io/examples/javascript/node_modules/mocha/lib/cli/run.js:375:5) 301: ##[warning]Attempt 1 failed. Reason: Child_process exited with error code 1 302: > [email protected] test 303: > npx mocha test/**/*.spec.js --timeout 60000 304: Exception during run: Error: Every node program run under Bazel must have a $RUNFILES_DIR, $RUNFILES or $RUNFILES_MANIFEST_FILE environment variable ... 326: at ModuleJob.run (node:internal/modules/esm/module_job:195:25) 327: at async ModuleLoader.import (node:internal/modules/esm/loader:337:24) 328: at async importModuleDynamicallyWrapper (node:internal/vm/module:432:15) 329: at async formattedImport (/Users/runner/work/seleniumhq.github.io/seleniumhq.github.io/examples/javascript/node_modules/mocha/lib/nodejs/esm-utils.js:9:14) 330: at async exports.requireOrImport (/Users/runner/work/seleniumhq.github.io/seleniumhq.github.io/examples/javascript/node_modules/mocha/lib/nodejs/esm-utils.js:42:28) 331: at async exports.loadFilesAsync (/Users/runner/work/seleniumhq.github.io/seleniumhq.github.io/examples/javascript/node_modules/mocha/lib/nodejs/esm-utils.js:100:20) 332: at async singleRun (/Users/runner/work/seleniumhq.github.io/seleniumhq.github.io/examples/javascript/node_modules/mocha/lib/cli/run-helpers.js:162:3) 333: at async exports.handler (/Users/runner/work/seleniumhq.github.io/seleniumhq.github.io/examples/javascript/node_modules/mocha/lib/cli/run.js:375:5) 334: ##[warning]Attempt 2 failed. Reason: Child_process exited with error code 1 335: > [email protected] test 336: > npx mocha test/**/*.spec.js --timeout 60000 337: Exception during run: Error: Every node program run under Bazel must have a $RUNFILES_DIR, $RUNFILES or $RUNFILES_MANIFEST_FILE environment variable ... 359: at ModuleJob.run (node:internal/modules/esm/module_job:195:25) 360: at async ModuleLoader.import (node:internal/modules/esm/loader:337:24) 361: at async importModuleDynamicallyWrapper (node:internal/vm/module:432:15) 362: at async formattedImport (/Users/runner/work/seleniumhq.github.io/seleniumhq.github.io/examples/javascript/node_modules/mocha/lib/nodejs/esm-utils.js:9:14) 363: at async exports.requireOrImport (/Users/runner/work/seleniumhq.github.io/seleniumhq.github.io/examples/javascript/node_modules/mocha/lib/nodejs/esm-utils.js:42:28) 364: at async exports.loadFilesAsync (/Users/runner/work/seleniumhq.github.io/seleniumhq.github.io/examples/javascript/node_modules/mocha/lib/nodejs/esm-utils.js:100:20) 365: at async singleRun (/Users/runner/work/seleniumhq.github.io/seleniumhq.github.io/examples/javascript/node_modules/mocha/lib/cli/run-helpers.js:162:3) 366: at async exports.handler (/Users/runner/work/seleniumhq.github.io/seleniumhq.github.io/examples/javascript/node_modules/mocha/lib/cli/run.js:375:5) 367: ##[error]Final attempt failed. Child_process exited with error 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.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

[renovate]

Autoclosing Skipped

This PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error.