From 1ffa214447073ead268af760d5db9c4d70faa04f Mon Sep 17 00:00:00 2001 From: Daphne Yang <139700604+daphne-sfdc@users.noreply.github.com> Date: Tue, 6 Feb 2024 09:53:33 -0500 Subject: [PATCH] chore: add comment for why we are using VSCode 1.85.2 for E2E tests (#5399) Co-authored-by: peternhale --- .github/workflows/runE2ETest.yml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/.github/workflows/runE2ETest.yml b/.github/workflows/runE2ETest.yml index 1ed84a2b4..515bf646e 100644 --- a/.github/workflows/runE2ETest.yml +++ b/.github/workflows/runE2ETest.yml @@ -25,6 +25,8 @@ jobs: os: [macos-latest, ubuntu-latest, windows-latest] nodeVersion: - 18.18.2 + # We are using VSCode version 1.85.2 instead of the latest version because of a WDIO bug. Starting from Chromedriver v115, the JSON endpoint was moved to a new URL, but WDIO is still trying to find the endpoint only at the old URL. VSCode 1.85.2 is the last supported version of VSCode because it uses Chromedriver v114, which is the last Chromedriver version that can be found using the old URL. VSCode 1.86.0 uses Chromedriver v118, which has an endpoint that can be found only at the new URL. + # We are using VSCode 1.85.2 for our E2E tests as a workaround until WDIO fixes this bug: https://github.com/webdriverio-community/wdio-vscode-service/pull/94 vscodeVersion: - 1.85.2 steps: