-
Notifications
You must be signed in to change notification settings - Fork 348
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release github-action
for Node.js node20
#968
Comments
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
github-action
for Node.js after node16
github-action
for Node.js node20
GitHub has announced that GitHub runner release v2.308.0 includes support for |
|
🎉 This issue has been resolved in version 6.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
@MikeMcC399 looks like it worked! |
|
This is an enhancement request for Cypress
github-action
.GitHub has now provided support for
node20
in their JavaScript Actions environment. See actions/runner#2704.What would you like?
A new major version of the Cypress
github-action
should be released using GitHub's support for Node.js20
in GitHub JavaScript Actions.Why is this needed?
Cypress needs to be able to run using Node.js
20
and not be restricted to Node.js16
.Node.js
16
reaches end-of-life on Sep 11, 2023.From within
github-action
, the full functionality of Cypress together with Cypress Cloud integration and test summaries is only available when Cypress is called bygithub-action
using the Cypress Module API. This is the default way that thegithub-action
calls Cypress since the release ofgithub-action@v2
. Cypress is called in the context of GitHub'sruns.using
for JavaScript Actions currently available only asnode16
.Other
This enhancement request has a critical dependency on an update to the
runs.using
for JavaScript Actions environment being provided by GitHub through their actions/runner.See actions/runner#2704 for announcement on the availability of
node20
support:Workarounds
The Custom test command option
command
ofgithub-action
can be used to call Cypress from the context of the Node.js version set up in the GitHub runner, for instance using actions/setup-node setting Node.js to18
or20
, however this usage bypasses many other functions ofgithub-action
. It causes many of the othergithub-action
options to be ignored and prevents return of detailed results information from the Cypress run, such as the test summary andresultsUrl
. Usingcommand
is therefore not a good long-term option.An alternative to using the Cypress JavaScript Action
github-action
is to call Cypress from a GitHub workflow directly usingrun
, with the same disadvantage as above.A further alternative is to call the Cypress Module API from a custom script written in JavaScript and called from a custom GitHub Actions workflow. This can be used in a simple way or the full results can be used and processed as needed.
Edit: Above text edited based on information in actions/runner#2704 Jul 19, 2023.
Updated again on Aug 15, 2023 based on actions/runner#2619 (comment).
Further update Aug 17, 2023.
The text was updated successfully, but these errors were encountered: