Mike McCready

- Possibly branch protection rules for `develop` need revisiting. - PR https://github.com/cypress-io/cypress/pull/30154 was clean in its own forked branch before merge, but has caused `yarn.lock` to become out of sync...

@raygdev > Was there something I could have done differently? I would like to make sure that for any future changes I make that this won't be a burden on...

> Yah, seems reasonable to have something in place since this keeps happening.

> Yah, seems reasonable to have something in place since this keeps happening.

This PR was merged without deduplication. Running the following against the `develop` branch produces changes related to `axios` and `follow-redirects`: ```shell yarn run yarn-deduplicate --strategy highest ``` I would leave...

@emilyrohrbough ```shell npx @puppeteer/browsers install --help ``` provides the following information: > --path Path to the root folder for the browser downloads and installation. The installation folder structure is >...

@REPLicated ```shell npx @puppeteer/browsers install chrome@stable ``` understands `stable` and `beta`. It also drops a file `.metadata` in the download directory, which currently would have the following contents: ```json {...

@mschile / @AtofStryker The issue which this PR is supposed to resolve is causing problems in GitHub self-hosted runners. After installing a selected Chrome browser version using the action [browser-actions/setup-chrome](https://github.com/browser-actions/setup-chrome),...

@Autobots631 It may not help, but you should at least be running on a supported version of Node.js, which means a minimum of `18.x`.

@Autobots631 Cypress `12.9.0` is not the latest version. The latest version is `13.14.2`, which @jennifer-shehane asked you to update to. You can find the latest version of Cypress on https://on.cypress.io/changelog...