Update dependency org.seleniumhq.selenium:selenium-java to v4.20.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
org.seleniumhq.selenium:selenium-java (source)	4.19.1 -> 4.20.0

---

Release Notes

SeleniumHQ/selenium (org.seleniumhq.selenium:selenium-java)

v4.20.0

---

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	622cdd1
🔍 Latest deploy log	https://app.netlify.com/sites/selenium-dev/deploys/662a116c99000f0008d51169
😎 Deploy Preview	https://deploy-preview-1689--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.

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

[qodo-merge-pro]

CI Failure Feedback

(Checks updated until commit 7e89c56)

Action: test_examples (windows-latest, nightly)

Failed stage: Run Tests Nightly Windows [❌]

Failure summary: The action failed due to an incorrect Maven command syntax in the build process. The error message indicates an "Unknown lifecycle phase '.version=4.21.0-SNAPSHOT'." This suggests that the Maven command was incorrectly formatted, likely due to an erroneous insertion of the version number directly into the command line, which Maven could not recognize as a valid lifecycle phase or goal.

Relevant error logs: 1: ##[group]Operating System 2: Microsoft Windows Server 2022 ... 167: $latest_snapshot = $xml_content.Content | xq '.content.data.\"content-item\"' | jq -r 'sort_by(.lastModified) | reverse | .[0] | .text' 168: Write-Output $latest_snapshot 169: cd examples/java 170: mvn -B -U test -Dselenium.version="$latest_snapshot" 171: 172: retry_wait_seconds: 10 173: polling_interval_seconds: 1 174: warning_on_retry: true 175: continue_on_error: false ... 198: Successfully installed PyYAML-6.0.1 tomlkit-0.12.4 xmltodict-0.13.0 yq-3.4.1 199: 4.21.0-SNAPSHOT 200: [INFO] Scanning for projects... 201: [INFO] 202: [INFO] -------------------< dev.selenium:selenium-examples >------------------- 203: [INFO] Building selenium-examples 1.0.0 204: [INFO] --------------------------------[ jar ]--------------------------------- 205: [INFO] ------------------------------------------------------------------------ 206: [INFO] BUILD FAILURE 207: [INFO] ------------------------------------------------------------------------ 208: [INFO] Total time: 0.829 s 209: [INFO] Finished at: [INFO] ------------------------------------------------------------------------ 210: [ERROR] Unknown lifecycle phase ".version=4.21.0-SNAPSHOT". You must specify a valid lifecycle phase or a goal in the format <plugin-prefix>:<goal> or <plugin-group-id>:<plugin-artifact-id>[:<plugin-version>]:<goal>. Available lifecycle phases are: validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify, install, deploy, pre-clean, clean, post-clean, pre-site, site, post-site, site-deploy. -> [Help 1] 211: [ERROR] 212: [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. 213: [ERROR] Re-run Maven using the -X switch to enable full debug logging. 214: [ERROR] 215: [ERROR] For more information about the errors and possible solutions, please read the following articles: 216: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/LifecyclePhaseNotFoundException 217: ##[warning]Attempt 1 failed. Reason: Child_process exited with error code 1 ... 222: Requirement already satisfied: argcomplete>=1.8.1 in c:\hostedtoolcache\windows\python\3.9.13\x64\lib\site-packages (from yq) (3.3.0) 223: 4.21.0-SNAPSHOT 224: [INFO] Scanning for projects... 225: [INFO] 226: [INFO] -------------------< dev.selenium:selenium-examples >------------------- 227: [INFO] Building selenium-examples 1.0.0 228: [INFO] --------------------------------[ jar ]--------------------------------- 229: [INFO] ------------------------------------------------------------------------ 230: [INFO] BUILD FAILURE 231: [INFO] ------------------------------------------------------------------------ 232: [INFO] Total time: 0.078 s 233: [INFO] Finished at: [INFO] ------------------------------------------------------------------------ 234: [ERROR] Unknown lifecycle phase ".version=4.21.0-SNAPSHOT". You must specify a valid lifecycle phase or a goal in the format <plugin-prefix>:<goal> or <plugin-group-id>:<plugin-artifact-id>[:<plugin-version>]:<goal>. Available lifecycle phases are: validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify, install, deploy, pre-clean, clean, post-clean, pre-site, site, post-site, site-deploy. -> [Help 1] 235: [ERROR] 236: [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. 237: [ERROR] Re-run Maven using the -X switch to enable full debug logging. 238: [ERROR] 239: [ERROR] For more information about the errors and possible solutions, please read the following articles: 240: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/LifecyclePhaseNotFoundException 241: ##[warning]Attempt 2 failed. Reason: Child_process exited with error code 1 ... 246: Requirement already satisfied: argcomplete>=1.8.1 in c:\hostedtoolcache\windows\python\3.9.13\x64\lib\site-packages (from yq) (3.3.0) 247: 4.21.0-SNAPSHOT 248: [INFO] Scanning for projects... 249: [INFO] 250: [INFO] -------------------< dev.selenium:selenium-examples >------------------- 251: [INFO] Building selenium-examples 1.0.0 252: [INFO] --------------------------------[ jar ]--------------------------------- 253: [INFO] ------------------------------------------------------------------------ 254: [INFO] BUILD FAILURE 255: [INFO] ------------------------------------------------------------------------ 256: [INFO] Total time: 0.078 s 257: [INFO] Finished at: [INFO] ------------------------------------------------------------------------ 258: [ERROR] Unknown lifecycle phase ".version=4.21.0-SNAPSHOT". You must specify a valid lifecycle phase or a goal in the format <plugin-prefix>:<goal> or <plugin-group-id>:<plugin-artifact-id>[:<plugin-version>]:<goal>. Available lifecycle phases are: validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify, install, deploy, pre-clean, clean, post-clean, pre-site, site, post-site, site-deploy. -> [Help 1] 259: [ERROR] 260: [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. 261: [ERROR] Re-run Maven using the -X switch to enable full debug logging. 262: [ERROR] 263: [ERROR] For more information about the errors and possible solutions, please read the following articles: 264: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/LifecyclePhaseNotFoundException 265: ##[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.