@cypress/github-action 5.6.1 → 5.7.0

package/README.md

@@ -1,12 +1,12 @@
-# cypress-io/github-action [![renovate-app badge][renovate-badge]][renovate-bot] [![Action status](https://github.com/cypress-io/github-action/workflows/main/badge.svg?branch=master)](https://github.com/cypress-io/github-action/actions)
+# cypress-io/github-action [![Action status][ci-badge]][ci-workflow] [![cypress][cloud-badge]][cloud-project] [![renovate-app badge][renovate-badge]][renovate-bot]
 
-> [GitHub Action](https://docs.github.com/en/actions) for running [Cypress](https://www.cypress.io) end-to-end and component tests. Includes NPM installation, custom caching and lots of configuration options.
+ > [GitHub Action](https://docs.github.com/en/actions) for running [Cypress](https://www.cypress.io) end-to-end and component tests. Includes npm, pnpm and Yarn installation, custom caching and lots of configuration options.
 
 ## Examples
 
 - [End-to-End](#end-to-end-testing) testing
 - [Component](#component-testing) testing
-- [Explicit version](#explicit-version)
+- Select [action version](#action-version)
 - Run tests in a given [browser](#browser)
   - using [Chrome](#chrome)
   - using [Firefox](#firefox)
@@ -17,8 +17,8 @@
 - Run only some [spec files](#specs)
 - Test [project in subfolder](#project)
 - [Record results](#record-test-results-on-cypress-cloud) on Cypress Cloud
-- Specify [auto cancel](#specify-auto-cancel-after-failures) after failures
 - Tag [recordings](#tag-recordings)
+- Specify [auto cancel](#specify-auto-cancel-after-failures) after failures
 - Store [test artifacts](#artifacts) on GitHub
 - [Quiet output](#quiet-flag)
 - Set Cypress [config values](#config)
@@ -29,31 +29,36 @@
 - [Start server](#start-server) before running the tests
 - [Start multiple servers](#start-multiple-servers) before running the tests
 - [Wait for server](#wait-on) to respond before running the tests
-- use [custom install command](#custom-install-command)
-- use [command prefix](#command-prefix)
-- use [own custom test command](#custom-test-command)
-- pass [custom build id](#custom-build-id) when recording to Cypress Cloud
-- generate a [robust custom build id](#robust-custom-build-id) to allow re-running the workflow
-- use different [working-directory](#working-directory)
-- use [pnpm](#pnpm)
-- use [Yarn Classic](#yarn-classic)
-- use [Yarn Modern](#yarn-modern)
-- use [Yarn workspaces](#yarn-workspaces)
-- use [custom cache key](#custom-cache-key)
-- run tests on multiple [Node versions](#node-versions)
-- split [install and tests](#split-install-and-tests) into separate jobs
-- use [custom install commands](#custom-install)
-- install [only Cypress](#install-cypress-only) to avoid installing all dependencies
-- [timeouts](#timeouts) to avoid hanging CI jobs
-- [print Cypress info](#print-cypress-info) like detected browsers
-- [run tests nightly](#nightly-tests) or on any schedule
-- [Suppress test summary](#suppress-test-summary)
-- [more examples](#more-examples)
+- [`wait-on` with Node.js 18+](#wait-on-with-nodejs-18) workarounds
+- Use [custom install command](#custom-install-command)
+- Use [command prefix](#command-prefix)
+- Use [own custom test command](#custom-test-command)
+- Pass [custom build id](#custom-build-id) when recording to Cypress Cloud
+- Generate a [robust custom build id](#robust-custom-build-id) to allow re-running the workflow
+- Use different [working-directory](#working-directory)
+- Use [subfolders](#subfolders)
+- Use [pnpm](#pnpm)
+- Use [Yarn Classic](#yarn-classic)
+- Use [Yarn Modern](#yarn-modern)
+- Use [Yarn Plug'n'Play](#yarn-plugnplay)
+- Use [Yarn workspaces](#yarn-workspaces)
+- Use [custom cache key](#custom-cache-key)
+- Run tests on multiple [Node versions](#node-versions)
+- Split [install and tests](#split-install-and-tests) into separate jobs
+- Use [custom install commands](#custom-install)
+- Install [only Cypress](#install-cypress-only) to avoid installing all dependencies
+- Use [timeouts](#timeouts) to avoid hanging CI jobs
+- Print [Cypress info](#print-cypress-info) like detected browsers
+- Run [tests nightly](#nightly-tests) or on any schedule
+- Suppress [test summary](#suppress-test-summary)
+- [More examples](#more-examples)
 
 Current examples contained in this repository are based on Cypress 12.x and can be found in the [examples](./examples) directory. Examples for [Legacy Configuration](https://on.cypress.io/guides/references/legacy-configuration) use Cypress `9.7.0` and are kept in the [examples/v9](./examples/v9) directory.
 
 Some older **external** examples, linked to by this document, are based solely on Cypress 9 and below and therefore use a [Legacy Configuration](https://on.cypress.io/guides/references/legacy-configuration). These may need modification to be applied to Cypress 10 and later. Each of these external links is listed with a `(legacy)` notation.
 
+**Note:** this package assumes that [cypress](https://www.npmjs.com/package/cypress) is declared as a development dependency in the [package.json](https://docs.npmjs.com/creating-a-package-json-file) file. The [cypress npm module](https://www.npmjs.com/package/cypress) is required to run Cypress via its [Module API](https://on.cypress.io/module-api).
+
 ### End-to-End Testing
 
 ```yml
@@ -65,7 +70,7 @@ jobs:
     steps:
       - name: Checkout
         uses: actions/checkout@v3
-      # Install NPM dependencies, cache them correctly
+      # Install npm dependencies, cache them correctly
       # and run all Cypress tests
       - name: Cypress run
         uses: cypress-io/github-action@v5
@@ -77,8 +82,6 @@ The workflow file [example-basic.yml](.github/workflows/example-basic.yml) shows
 
 This workflow uses the default [test type](https://on.cypress.io/guides/overview/why-cypress#Test-types) of [End-to-End (E2E) Testing](https://on.cypress.io/guides/overview/why-cypress#End-to-end). Alternatively, [Component Testing](https://on.cypress.io/guides/overview/why-cypress#Component) can be utilized by referencing the [Component Testing](#component-testing) section below.
 
-**Note:** this package assumes that `cypress` is declared as a development dependency in the `package.json` file. The `cypress` NPM module is required to run Cypress via its [NPM module API](https://on.cypress.io/module-api).
-
 ### Component Testing
 
 To use [Cypress Component Testing](https://on.cypress.io/component-testing) add `component: true`
@@ -102,25 +105,27 @@ jobs:
 
 See the example project [component-tests](examples/component-tests/) and the [example-component-test.yml](.github/workflows/example-component-test.yml) workflow for more details.
 
-### Explicit version
+### Action version
 
 **Best practice:**
 
-Our examples specify the tag of the action to use listing only the major version `@v5`
+Our examples specify using branch [v5](https://github.com/cypress-io/github-action/tree/v5) which is the action's latest major version:
 
 ```yml
 - name: Cypress run
   uses: cypress-io/github-action@v5
 ```
 
-When using `cypress-io/github-action@v5` from your workflow file, you automatically will be using the latest [tagged version from this repository](https://github.com/cypress-io/github-action/tags). If you want to precisely control the version of this module, use the full tag version, for example:
+When using `cypress-io/github-action@v5` from your workflow file, you will automatically use the latest [tag](https://github.com/cypress-io/github-action/tags) from branch [v5](https://github.com/cypress-io/github-action/tree/v5).
+
+Alternatively, to mitigate unforeseen breaks, bind to a specific [tag](https://github.com/cypress-io/github-action/tags), for example:
 
 ```yml
 - name: Cypress run
   uses: cypress-io/github-action@v5.1.0
 ```
 
-By using the full version tag, you will avoid accidentally using a newer version of the action.
+The changes associated with each tag are shown under GitHub's [releases](https://github.com/cypress-io/github-action/releases) list. Refer also to the [Changelog](#changelog) for an overview of major changes.
 
 ### Browser
 
@@ -279,15 +284,15 @@ jobs:
       - name: Cypress run
         uses: cypress-io/github-action@v5
         with:
-          spec: cypress/integration/spec1.js
+          spec: cypress/e2e/spec1.cy.js
 ```
 
 You can pass multiple specs and wild card patterns using multi-line parameter, see [example-config.yml](./.github/workflows/example-config.yml):
 
 ```yml
 spec: |
-  cypress/integration/spec-a.js
-  cypress/**/*-b.js
+  cypress/e2e/spec-a.cy.js
+  cypress/**/*-b.cy.js
 ```
 
 For more information, visit [the Cypress command-line docs](https://on.cypress.io/command-line#cypress-run-env-lt-env-gt).
@@ -372,30 +377,6 @@ jobs:
           CYPRESS_PROJECT_ID: ${{ secrets.PROJECT_ID }}
 ```
 
-### Quiet flag
-
-You can provide `quiet` flag for cypress run to silence any Cypress specific output from stdout
-
-```yml
-name: example-quiet
-on: push
-jobs:
-  cypress-run:
-    runs-on: ubuntu-22.04
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v3
-      # Install NPM dependencies, cache them correctly
-      # and run all Cypress tests with `quiet` parameter
-      - name: Cypress run
-        uses: ./
-        with:
-          working-directory: examples/quiet
-          quiet: true
-```
-
-[![example-quiet](https://github.com/cypress-io/github-action/workflows/example-quiet/badge.svg?branch=master)](.github/workflows/example-quiet.yml)
-
 ### Tag recordings
 
 You can pass a single or multiple tags when recording a run. For example
@@ -409,7 +390,7 @@ jobs:
     # let's make sure our "app" works on several versions of Node
     strategy:
       matrix:
-        node: [14, 16, 18, 19]
+        node: [16, 18, 19, 20]
     name: E2E on Node v${{ matrix.node }}
     steps:
       - name: Setup Node
@@ -503,6 +484,30 @@ jobs:
           path: cypress/videos
 ```
 
+### Quiet flag
+
+You can provide `quiet` flag for cypress run to silence any Cypress specific output from stdout
+
+```yml
+name: example-quiet
+on: push
+jobs:
+  cypress-run:
+    runs-on: ubuntu-22.04
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v3
+      # Install npm dependencies, cache them correctly
+      # and run all Cypress tests with `quiet` parameter
+      - name: Cypress run
+        uses: ./
+        with:
+          working-directory: examples/quiet
+          quiet: true
+```
+
+[![example-quiet](https://github.com/cypress-io/github-action/workflows/example-quiet/badge.svg?branch=master)](.github/workflows/example-quiet.yml)
+
 ### Config
 
 Specify [configuration](https://docs.cypress.io/guides/references/configuration.html) values with `config` parameter
@@ -549,9 +554,9 @@ jobs:
 
 ### Parallel
 
-**Note:** Cypress parallelization requires [Cypress Cloud](https://on.cypress.io/dashboard-introduction) account.
+**Note:** Cypress parallelization requires a [Cypress Cloud](https://on.cypress.io/dashboard-introduction) account.
 
-You can spin multiple containers running in parallel using `strategy: matrix` argument. Just add more dummy items to the `containers: [1, 2, ...]` array to spin more free or paid containers. Then use `record` and `parallel` parameters to [load balance tests](https://on.cypress.io/parallelization)
+You can spin multiple containers running in parallel using `strategy: matrix` argument. Just add more dummy items to the `containers: [1, 2, ...]` array to spin more free or paid containers. Then use `record` and `parallel` parameters to [load balance tests](https://on.cypress.io/parallelization).
 
 ```yml
 name: Parallel Cypress Tests
@@ -591,9 +596,11 @@ jobs:
 
 ![Parallel run](images/parallel.png)
 
-**Warning ⚠️:** Cypress actions use `GITHUB_TOKEN` to get the correct branch and the number of jobs run, making it possible to re-run without the need of pushing an empty commit. If you don't want to use the `GITHUB_TOKEN` you can still run your tests without problem with the only note that Cypress Cloud's API connects parallel jobs into a single logical run using GitHub commit SHA plus workflow name. If you attempt to re-run GitHub checks, Cypress Cloud thinks the run has already ended. In order to truly rerun parallel jobs, push an empty commit with `git commit --allow-empty -m "re-run checks" && git push`. As another work around you can generate and cache a custom build id, read [Adding a unique build number to GitHub Actions](https://medium.com/attest-engineering/adding-a-unique-github-build-identifier-7aa2e83cadca)
+**Warning ⚠️:** Cypress actions use `GITHUB_TOKEN` to get the correct branch and the number of jobs run, making it possible to re-run without the need of pushing an empty commit. If you don't want to use the `GITHUB_TOKEN` you can still run your tests without problem with the only note that Cypress Cloud's API connects parallel jobs into a single logical run using GitHub commit SHA plus workflow name. If you attempt to re-run GitHub checks, Cypress Cloud thinks the run has already ended. In order to truly rerun parallel jobs, push an empty commit with `git commit --allow-empty -m "re-run checks" && git push`. As another work around you can generate and cache a custom build id, read [Adding a unique build number to GitHub Actions](https://medium.com/attest-engineering/adding-a-unique-github-build-identifier-7aa2e83cadca).
+
+The Cypress GH Action does not spawn or create any additional containers - it only links the multiple containers spawned using the matrix strategy into a single logical Cypress Cloud run where it splits the specs amongst the machines. See the [Cypress parallelization](https://on.cypress.io/parallelization) guide for the explanation.
 
-The Cypress GH Action does not spawn or create any additional containers - it only links the multiple containers spawned using the matrix strategy into a single logical Cypress Cloud run and into splitting the specs amongst the machines. See the [Cypress parallelization](https://on.cypress.io/parallelization) guide for the explanation.
+During staged rollout of a new GitHub-hosted runner version, GitHub may provide a mixture of current and new image versions used by the container matrix. It is recommended to use a [Docker image](#docker-image) in the parallel job run which avoids any Cypress Cloud errors due to browser major version mismatch from the two different image versions. A [Docker image](#docker-image) is not necessary if testing against the default built-in Electron browser because this browser version is fixed by the Cypress version in use and it is unaffected by any GitHub runner image rollout.
 
 ### Component and E2E Testing
 
@@ -812,7 +819,7 @@ jobs:
 
 ### Custom test command
 
-You can overwrite the Cypress run command with your own
+You can overwrite the Cypress run command with your own command.
 
 ```yml
 steps:
@@ -825,6 +832,8 @@ steps:
       command: npm run e2e:ci
 ```
 
+**Caution**: using the action parameter `command` causes multiple other parameters to be ignored including: `auto-cancel-after-failures`, `browser`, `ci-build-id`, `command-prefix`, `component`, `config`, `config-file`, `env`, `group`, `headed`, `parallel`, `project`, `publish-summary`, `quiet`, `record`, `spec` and `tag`.
+
 See [.github/workflows/example-custom-command.yml](.github/workflows/example-custom-command.yml) file.
 
 ### Custom build id
@@ -1069,6 +1078,31 @@ See [example-yarn-modern.yml](.github/workflows/example-yarn-modern.yml) for an
 
 [![Yarn Modern example](https://github.com/cypress-io/github-action/workflows/example-yarn-modern/badge.svg?branch=master)](.github/workflows/example-yarn-modern.yml)
 
+### Yarn Plug'n'Play
+
+When using [Yarn Modern](https://yarnpkg.com/) (Yarn 2 and later) with [Plug'n'Play](https://yarnpkg.com/features/pnp) enabled, you will need to use the `command` parameter to run [yarn dlx](https://yarnpkg.com/cli/dlx) instead of [npx](https://docs.npmjs.com/cli/v9/commands/npx).
+
+```yaml
+name: example-yarn-modern-pnp
+on: push
+jobs:
+  yarn-classic:
+    runs-on: ubuntu-22.04
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v3
+      - name: Cypress run
+        uses: cypress-io/github-action@v5
+        with:
+          working-directory: examples/yarn-modern-pnp
+          install-command: yarn install
+          command: yarn dlx cypress run
+```
+
+[![Yarn Plug'n'Play example](https://github.com/cypress-io/github-action/actions/workflows/example-yarn-modern-pnp.yml/badge.svg?branch=master)](https://github.com/cypress-io/github-action/actions/workflows/example-yarn-modern-pnp.yml)
+
+**Caution**: using the action parameter `command` causes multiple other parameters to be ignored. [See `command` section for more information.](#custom-test-command)
+
 ### Yarn workspaces
 
 This action should discover the Yarn workspaces correctly. For example, see folder [examples/start-and-yarn-workspaces](examples/start-and-yarn-workspaces) and workflow file [example-start-and-yarn-workspaces.yml](.github/workflows/example-start-and-yarn-workspaces.yml)
@@ -1107,7 +1141,7 @@ jobs:
     # let's make sure our "app" works on several versions of Node
     strategy:
       matrix:
-        node: [14, 16, 18, 19]
+        node: [16, 18, 19, 20]
     name: E2E on Node v${{ matrix.node }}
     steps:
       - name: Setup Node
@@ -1141,7 +1175,7 @@ jobs:
     runs-on: ubuntu-22.04
     strategy:
       matrix:
-        node: [14, 16, 18, 19]
+        node: [16, 18, 19, 20]
     name: E2E on Node v${{ matrix.node }}
     steps:
       - uses: actions/setup-node@v3
@@ -1184,7 +1218,7 @@ See [cypress-gh-action-monorepo](https://github.com/bahmutov/cypress-gh-action-m
 
 ### Custom install
 
-Finally, you might not need this GH Action at all. For example, if you want to split the NPM dependencies installation from the Cypress binary installation, then it makes no sense to use this action. Instead you can install and cache Cypress yourself. See [cypress-gh-action-split-install](https://github.com/bahmutov/cypress-gh-action-split-install) (legacy) for a working example.
+Finally, you might not need this GH Action at all. For example, if you want to split the npm dependencies installation from the Cypress binary installation, then it makes no sense to use this action. Instead you can install and cache Cypress yourself. See [cypress-gh-action-split-install](https://github.com/bahmutov/cypress-gh-action-split-install) (legacy) for a working example.
 
 ### Install Cypress only
 
@@ -1237,7 +1271,7 @@ See [cypress-gh-action-example](https://github.com/bahmutov/cypress-gh-action-ex
 | [cypress-gh-action-example](https://github.com/bahmutov/cypress-gh-action-example)  (legacy)            | Uses Yarn, and runs in parallel on several versions of Node, different browsers, and more |
 | [cypress-gh-action-monorepo](https://github.com/bahmutov/cypress-gh-action-monorepo)                    | Splits install and running tests commands, runs Cypress from sub-folder                   |
 | [cypress-gh-action-subfolders](https://github.com/bahmutov/cypress-gh-action-subfolders) (legacy)       | Has separate folder for Cypress dependencies                                              |
-| [cypress-gh-action-split-install](https://github.com/bahmutov/cypress-gh-action-split-install) (legacy) | Only install NPM dependencies, then install and cache Cypress binary yourself             |
+| [cypress-gh-action-split-install](https://github.com/bahmutov/cypress-gh-action-split-install) (legacy) | Only install npm dependencies, then install and cache Cypress binary yourself             |
 | [cypress-gh-action-changed-files](https://github.com/bahmutov/cypress-gh-action-changed-files) (legacy) | Shows how to run different Cypress projects depending on changed files                    |
 | [cypress-examples](https://github.com/bahmutov/cypress-examples)                                        | Shows separate install job from parallel test jobs                                        |
 | [cypress-gh-action-split-jobs](https://github.com/bahmutov/cypress-gh-action-split-jobs) (legacy)       | Shows a separate install job with the build step, and another job that runs the tests     |
@@ -1257,16 +1291,6 @@ This action installs local dependencies using lock files. Ensure that exactly on
 
 See section [Yarn Modern](#yarn-modern) for information about using Yarn version 2 and later.
 
-#### Node.js Support
-
-Node.js is required to run this action. The current version `v5` supports:
-
-- **Node.js** 14.x
-- **Node.js** 16.x
-- **Node.js** 18.x and above
-
-and is generally aligned with [Node.js's release schedule](https://github.com/nodejs/Release).
-
 ## Debugging
 
 This action uses the [debug](https://github.com/visionmedia/debug#readme) module to output additional verbose logs. You can see these debug messages by setting the following environment variable:
@@ -1318,10 +1342,6 @@ pinging url https://example.cypress.io for 30 seconds
 ::debug::pinging https://example.cypress.io has finished ok
 ```
 
-## Development
-
-Read [DEVELOPMENT.md](DEVELOPMENT.md)
-
 ## More information
 
 - Read our blog post [Drastically Simplify Testing on CI with Cypress GitHub Action](https://www.cypress.io/blog/2019/11/20/drastically-simplify-your-testing-with-cypress-github-action/)
@@ -1456,24 +1476,49 @@ jobs:
           publish-summary: false
 ```
 
+## Node.js Support
+
+Node.js is required to run this action. The current version `v5` supports:
+
+- **Node.js** 16.x
+- **Node.js** 18.x and above
+
+and is generally aligned with [Node.js's release schedule](https://github.com/nodejs/Release).
+
 ## Changelog
 
 See [Releases](https://github.com/cypress-io/github-action/releases) for full details of changes.
 
-| Version | Changes                                                                                                                                  |
-| ------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
-| v5      | Examples and workflows additionally use Node.js 18. Use of the end-of-life Node.js version 12 in examples and workflows is removed.      |
-| v4.2.0  | Support for pnpm added.                                                                                      |
-| v4      | Support for Cypress 10 and later versions is added.                                                                                      |
-| v3      | Action runs under Node.js 16 instead of Node.js 12.                                                                                      |
-| v2      | Cypress runs using the [NPM module API](https://docs.cypress.io/guides/guides/module-api) instead of being started via the command line. |
-| v1      | *This version is no longer runnable in GitHub due to security changes.*                                                                  |
+| Version | Changes                                                                                                                              |
+| ------- | ------------------------------------------------------------------------------------------------------------------------------------ |
+| v5.6.2  | Examples add Node.js 20. End of support and removal of Node.js 14 examples.                                                          |
+| v5.2.0  | Examples add Node.js 19.                                                                                                             |
+| v5.0.0  | Examples add Node.js 18 and remove Node.js 12.                                                                                       |
+| v4.2.2  | Dependency on GitHub `set-output` workflow command removed.                                                                          |
+| v4.2.0  | Support for `pnpm` added.                                                                                                            |
+| v4.0.0  | Support for Cypress 10 and later versions added.                                                                                     |
+| v3      | Action runs under Node.js 16 instead of Node.js 12.                                                                                  |
+| v2      | Cypress runs using the [Module API](https://docs.cypress.io/guides/guides/module-api) instead of being started via the command line. |
+| v1      | *This version is no longer runnable in GitHub due to security changes.*                                                              |
 
 *Note: [GitHub announced](https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/) their plan to disable `save-state` and `set-output` commands by May 31, 2023. This will prevent [cypress-io/github-action](https://github.com/cypress-io/github-action) version [v4.2.1](https://github.com/cypress-io/github-action/releases/tag/v4.2.1), and earlier, running after this date since they use `set-output`. Affected users should update to using `v5` of the [cypress-io/github-action](https://github.com/cypress-io/github-action) action before the deadline.*
 
+## Contributing
+
+Please see our [Contributing Guideline](./CONTRIBUTING.md) which explains how to contribute fixes or features to the repo and how to test.
+
 ## License
 
-[MIT License](./LICENSE.md)
+[![license][license-badge]][license-file]
+
+This project is licensed under the terms of the [MIT license][license-file].
 
+<!-- badge links follow -->
+[ci-badge]: https://github.com/cypress-io/github-action/workflows/main/badge.svg?branch=master
+[ci-workflow]: https://github.com/cypress-io/github-action/actions/workflows/main.yml
+[cloud-badge]: https://img.shields.io/endpoint?url=https://cloud.cypress.io/badge/simple/3tb7jn/master&style=flat&logo=cypress
+[cloud-project]: https://cloud.cypress.io/projects/3tb7jn/runs
 [renovate-badge]: https://img.shields.io/badge/renovate-app-blue.svg
 [renovate-bot]: https://github.com/renovatebot
+[license-badge]: https://img.shields.io/badge/license-MIT-green.svg
+[license-file]: ./LICENSE.md

package/action.yml

@@ -1,7 +1,7 @@
 # https://help.github.com/en/actions/automating-your-workflow-with-github-actions/metadata-syntax-for-github-actions
 name: 'Cypress.io'
-description: 'GitHub Action for running Cypress end-to-end tests'
-author: 'Gleb Bahmutov'
+description: 'GitHub Action for running Cypress end-to-end and component tests'
+author: 'Cypress-io'
 inputs:
   record:
     description: 'Sends test results to Cypress Dashboard'

package/dist/index.js

@@ -75008,10 +75008,6 @@ const runTests = async () => {
     quiet: getInputBool('quiet'),
     component: getInputBool('component')
   }
-  const cypressModulePath =
-    require.resolve('cypress', { paths: [workingDirectory] }) ||
-    'cypress'
-  const cypress = require(cypressModulePath)
   const runTests = getInputBool('runTests', true)
   const spec = getSpecsList()
 
@@ -75033,6 +75029,11 @@ const runTests = async () => {
     return runTestsUsingCommandLine()
   }
 
+  const cypressModulePath =
+    require.resolve('cypress', { paths: [workingDirectory] }) ||
+    'cypress'
+  const cypress = require(cypressModulePath)
+
   debug('Running Cypress tests using NPM module API')
   debug(`requiring cypress dependency, cwd is ${process.cwd()}`)
   debug(`working directory ${workingDirectory}`)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cypress/github-action",
-  "version": "5.6.1",
+  "version": "5.7.0",
   "description": "GitHub Action for running Cypress end-to-end and component tests",
   "private": false,
   "main": "dist/index.js",
@@ -25,7 +25,7 @@
     "actions",
     "cypress-io"
   ],
-  "author": "Gleb Bahmutov <gleb@cypress.io>",
+  "author": "Cypress-io",
   "license": "MIT",
   "bugs": {
     "url": "https://github.com/cypress-io/github-action/issues"
@@ -46,10 +46,10 @@
     "supports-color": "9.3.1"
   },
   "devDependencies": {
-    "@types/node": "18.15.10",
+    "@types/node": "18.16.1",
     "@vercel/ncc": "0.36.1",
     "husky": "8.0.3",
-    "markdown-link-check": "3.11.0",
+    "markdown-link-check": "3.11.1",
     "prettier": "2.8.4"
   },
   "publishConfig": {