Error: could not start chrome.

[SOMERSOFTAndrewCrook]

The following error is now being displayed

Application started in SUPER mode. All restrictions removed.
MongoDB not established. Start mongo on port 27017 to persist data and restart or use the `initDbConnection` method.
Server ready at http://localhost:3280
GraphQL server ready at http://localhost:3280/graphql
Subscriptions ready at ws://localhost:3280/graphql
gRPC server running at http://127.0.0.1:50052/
(node:1936) DeprecationWarning: Calling start() is no longer necessary. It can be safely omitted.
gRPC server running at 0.0.0.0:50053
(Use `node --trace-deprecation ...` to show where the warning was created)
(node:1936) DeprecationWarning: Calling start() is no longer necessary. It can be safely omitted.
gRPC server running at 0.0.0.0:50051
public - gRPC server running at 0.0.0.0:50050
Error: could not start chrome. Check to see if chrome is downloaded on the system. Error: Executable doesn't exist at /home/runner/.cache/ms-playwright/chromium_headless_shell-1148/chrome-linux/headless_shell
╔═════════════════════════════════════════════════════════════════════════╗
║ Looks like Playwright Test or Playwright was just installed or updated. ║
║ Please run the following command to download new browsers:              ║
║                                                                         ║
║     npx playwright install                                              ║
║                                                                         ║
║ <3 Playwright Team                                                      ║
╚═════════════════════════════════════════════════════════════════════════╝ Failed to launch browser.
    at executablePathOrDie (/usr/local/lib/node_modules/@a11ywatch/a11ywatch/node_modules/playwright-core/lib/server/registry/index.js:394:15)
    at Object.executablePathOrDie (/usr/local/lib/node_modules/@a11ywatch/a11ywatch/node_modules/playwright-core/lib/server/registry/index.js:424:43)
    at Chromium._launchProcess (/usr/local/lib/node_modules/@a11ywatch/a11ywatch/node_modules/playwright-core/lib/server/browserType.js:203:39)
    at async Chromium._innerLaunch (/usr/local/lib/node_modules/@a11ywatch/a11ywatch/node_modules/playwright-core/lib/server/browserType.js:139:9)
    at async Chromium._innerLaunchWithRetries (/usr/local/lib/node_modules/@a11ywatch/a11ywatch/node_modules/playwright-core/lib/server/browserType.js:120:14)
    at async ProgressController.run (/usr/local/lib/node_modules/@a11ywatch/a11ywatch/node_modules/playwright-core/lib/server/progress.js:79:22)
    at async Chromium.launch (/usr/local/lib/node_modules/@a11ywatch/a11ywatch/node_modules/playwright-core/lib/server/browserType.js:79:21)
    at async BrowserServerLauncherImpl.launchServer (/usr/local/lib/node_modules/@a11ywatch/a11ywatch/node_modules/playwright-core/lib/browserServerImpl.js:48:21)
    at async BrowserType.launchServer (/usr/local/lib/node_modules/@a11ywatch/a11ywatch/node_modules/playwright-core/lib/client/browserType.js:82:12)
Retry connection error TypeError: Cannot use 'in' operator to search for 'endpointURL' in undefined

The last working run was on 14th December 2024 and the first error was on 21st December 2024.

There is also a deprecation warning.

Deprecation notice: v1, v2, and v3 of the artifact actions
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "Audit Results".
Please update your workflow to use v4 of the artifact actions.
Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/

[gcharest]

We had a similar error and there are two commits after the last release:

v2.1.10...main

If you set your action with the pinned hash 0c8d05657a89863a4620b277e0b50ed87a8ca466 that should include the fix for the dependency.