Workaround for chromedriver domain name change

[paymand]

Proposed changes

Workaround for chromedriver domain name change.
Fixes #12251 for v8.

Types of changes

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update

Checklist

• I have read the CONTRIBUTING doc
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)
• I have added proper type definitions for new commands (if appropriate)

Further comments

Reviewers: @webdriverio/project-committers

[christian-bromann]

Thanks a lot 👍

[wdio-bot]

Hey paymand 👋

Thank you for your contribution to WebdriverIO! Your pull request has been marked as an "Expensable" contribution. We've sent you an email with further instructions on how to claim your expenses from our development fund. Please make sure to check your spam folder as well. If you have any questions, feel free to reach out to us at expense@webdriver.io or in the contributing channel on Discord.

We are looking forward to more contributions from you in the future 🙌

Have a nice day,
The WebdriverIO Team 🤖

[Abel0916]

Thanks for the quick fixing. It looks like there is no new V8 version published to include this fixing. @christian-bromann Will you publish a new version? Thanks.

[christian-bromann]

Yes, eventually later today or tomorrow latest.

[SinghMegha27]

Is this a workaround for this error error Downloading Chromedriver v121.0.6167.185
2024-02-18T14:50:45.738Z WARN webdriver: Chromedriver v121.0.6167.185 don't exist, trying to find known good version.. ?

[christian-bromann]

@SinghMegha27 this is related to a different issue which WebdriverIO has an internal workaround for, it should still be able to find the right version for you.