chore(deps): update dependency selenium to v4.27.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
selenium	==4.27.0 -> ==4.27.1

---

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.

[netlify]

✅ Deploy Preview for selenium-dev ready!

Name	Link
🔨 Latest commit	fd68122
🔍 Latest deploy log	https://app.netlify.com/sites/selenium-dev/deploys/67461c82ca6f640008920035
😎 Deploy Preview	https://deploy-preview-2075--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 0435c0c)

Action: tests (windows, stable, 3.9)

Failed stage: Run tests [❌]

Failed test name: tests/bidi/cdp/test_network.py

Failure summary: The action failed due to the following reasons: An ImportError occurred while collecting the test module tests/bidi/cdp/test_network.py. The error was caused by a ModuleNotFoundError indicating that the module selenium.webdriver.common.devtools.v128 could not be found. There were warnings related to unknown pytest marks in tests/bidi/test_bidi_logging.py. The mark pytest.mark.driver_type was not recognized, which suggests it might be a typo or a custom mark that needs to be registered.

Relevant error logs: 1: ##[group]Operating System 2: Microsoft Windows Server 2022 ... 294: timeout_minutes: 60 295: max_attempts: 3 296: command: cd examples/python 297: pytest --reruns 3 298: 299: retry_wait_seconds: 10 300: polling_interval_seconds: 1 301: warning_on_retry: true 302: continue_on_error: false ... 311: Python3_ROOT_DIR: C:\hostedtoolcache\windows\Python\3.9.13\x64 312: JAVA_HOME: C:\hostedtoolcache\windows\Java_Temurin-Hotspot_jdk\11.0.25-9\x64 313: JAVA_HOME_11_X64: C:\hostedtoolcache\windows\Java_Temurin-Hotspot_jdk\11.0.25-9\x64 314: ##[endgroup] 315: ============================= test session starts ============================= 316: platform win32 -- Python 3.9.13, pytest-8.3.3, pluggy-1.5.0 317: rootdir: D:\a\seleniumhq.github.io\seleniumhq.github.io\examples\python 318: plugins: rerunfailures-15.0, trio-0.8.0 319: collected 138 items / 1 error 320: =================================== ERRORS ==================================== 321: _______________ ERROR collecting tests/bidi/cdp/test_network.py _______________ 322: ImportError while importing test module 'D:\a\seleniumhq.github.io\seleniumhq.github.io\examples\python\tests\bidi\cdp\test_network.py'. 323: Hint: make sure your test modules/packages have valid Python names. 324: Traceback: 325: C:\hostedtoolcache\windows\Python\3.9.13\x64\lib\importlib\__init__.py:127: in import_module 326: return _bootstrap._gcd_import(name[level:], package, level) 327: tests\bidi\cdp\test_network.py:5: in <module> 328: from selenium.webdriver.common.devtools.v128.network import Headers 329: E ModuleNotFoundError: No module named 'selenium.webdriver.common.devtools.v128' ... 337: tests\bidi\test_bidi_logging.py:30 338: D:\a\seleniumhq.github.io\seleniumhq.github.io\examples\python\tests\bidi\test_bidi_logging.py:30: PytestUnknownMarkWarning: Unknown pytest.mark.driver_type - is this a typo? You can register custom marks to avoid this warning - for details, see https://docs.pytest.org/en/stable/how-to/mark.html 339: @pytest.mark.driver_type("bidi") 340: tests\bidi\test_bidi_logging.py:42 341: D:\a\seleniumhq.github.io\seleniumhq.github.io\examples\python\tests\bidi\test_bidi_logging.py:42: PytestUnknownMarkWarning: Unknown pytest.mark.driver_type - is this a typo? You can register custom marks to avoid this warning - for details, see https://docs.pytest.org/en/stable/how-to/mark.html 342: @pytest.mark.driver_type("bidi") 343: -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html 344: =========================== short test summary info =========================== 345: ERROR tests/bidi/cdp/test_network.py 346: !!!!!!!!!!!!!!!!!!! Interrupted: 1 error during collection !!!!!!!!!!!!!!!!!!!! 347: ======================== 4 warnings, 1 error in 45.93s ======================== 348: ##[warning]Attempt 1 failed. Reason: Child_process exited with error code 1 349: ============================= test session starts ============================= 350: platform win32 -- Python 3.9.13, pytest-8.3.3, pluggy-1.5.0 351: rootdir: D:\a\seleniumhq.github.io\seleniumhq.github.io\examples\python 352: plugins: rerunfailures-15.0, trio-0.8.0 353: collected 138 items / 1 error 354: =================================== ERRORS ==================================== 355: _______________ ERROR collecting tests/bidi/cdp/test_network.py _______________ 356: ImportError while importing test module 'D:\a\seleniumhq.github.io\seleniumhq.github.io\examples\python\tests\bidi\cdp\test_network.py'. 357: Hint: make sure your test modules/packages have valid Python names. 358: Traceback: 359: C:\hostedtoolcache\windows\Python\3.9.13\x64\lib\importlib\__init__.py:127: in import_module 360: return _bootstrap._gcd_import(name[level:], package, level) 361: tests\bidi\cdp\test_network.py:5: in <module> 362: from selenium.webdriver.common.devtools.v128.network import Headers 363: E ModuleNotFoundError: No module named 'selenium.webdriver.common.devtools.v128' ... 371: tests\bidi\test_bidi_logging.py:30 372: D:\a\seleniumhq.github.io\seleniumhq.github.io\examples\python\tests\bidi\test_bidi_logging.py:30: PytestUnknownMarkWarning: Unknown pytest.mark.driver_type - is this a typo? You can register custom marks to avoid this warning - for details, see https://docs.pytest.org/en/stable/how-to/mark.html 373: @pytest.mark.driver_type("bidi") 374: tests\bidi\test_bidi_logging.py:42 375: D:\a\seleniumhq.github.io\seleniumhq.github.io\examples\python\tests\bidi\test_bidi_logging.py:42: PytestUnknownMarkWarning: Unknown pytest.mark.driver_type - is this a typo? You can register custom marks to avoid this warning - for details, see https://docs.pytest.org/en/stable/how-to/mark.html 376: @pytest.mark.driver_type("bidi") 377: -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html 378: =========================== short test summary info =========================== 379: ERROR tests/bidi/cdp/test_network.py 380: !!!!!!!!!!!!!!!!!!! Interrupted: 1 error during collection !!!!!!!!!!!!!!!!!!!! 381: ======================== 4 warnings, 1 error in 9.36s ========================= 382: ##[warning]Attempt 2 failed. Reason: Child_process exited with error code 1 383: ============================= test session starts ============================= 384: platform win32 -- Python 3.9.13, pytest-8.3.3, pluggy-1.5.0 385: rootdir: D:\a\seleniumhq.github.io\seleniumhq.github.io\examples\python 386: plugins: rerunfailures-15.0, trio-0.8.0 387: collected 138 items / 1 error 388: =================================== ERRORS ==================================== 389: _______________ ERROR collecting tests/bidi/cdp/test_network.py _______________ 390: ImportError while importing test module 'D:\a\seleniumhq.github.io\seleniumhq.github.io\examples\python\tests\bidi\cdp\test_network.py'. 391: Hint: make sure your test modules/packages have valid Python names. 392: Traceback: 393: C:\hostedtoolcache\windows\Python\3.9.13\x64\lib\importlib\__init__.py:127: in import_module 394: return _bootstrap._gcd_import(name[level:], package, level) 395: tests\bidi\cdp\test_network.py:5: in <module> 396: from selenium.webdriver.common.devtools.v128.network import Headers 397: E ModuleNotFoundError: No module named 'selenium.webdriver.common.devtools.v128' ... 405: tests\bidi\test_bidi_logging.py:30 406: D:\a\seleniumhq.github.io\seleniumhq.github.io\examples\python\tests\bidi\test_bidi_logging.py:30: PytestUnknownMarkWarning: Unknown pytest.mark.driver_type - is this a typo? You can register custom marks to avoid this warning - for details, see https://docs.pytest.org/en/stable/how-to/mark.html 407: @pytest.mark.driver_type("bidi") 408: tests\bidi\test_bidi_logging.py:42 409: D:\a\seleniumhq.github.io\seleniumhq.github.io\examples\python\tests\bidi\test_bidi_logging.py:42: PytestUnknownMarkWarning: Unknown pytest.mark.driver_type - is this a typo? You can register custom marks to avoid this warning - for details, see https://docs.pytest.org/en/stable/how-to/mark.html 410: @pytest.mark.driver_type("bidi") 411: -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html 412: =========================== short test summary info =========================== 413: ERROR tests/bidi/cdp/test_network.py 414: !!!!!!!!!!!!!!!!!!! Interrupted: 1 error during collection !!!!!!!!!!!!!!!!!!!! 415: ======================== 4 warnings, 1 error in 9.33s ========================= 416: ##[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.