-
Notifications
You must be signed in to change notification settings - Fork 338
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
Cypress does not pick up Node version set by Action #467
Comments
Thanks for reporting @sergiubcn - just like to add we're seeing exactly the same behaviour in our workflows. |
Is that fixed now? I am seeing the same issue when I update cypress to 9.* |
There's another issue filed for this, with a proposed (temporary) workaround: #489 (comment) |
This is an old issue and I wanted to give you some feedback that what you describe is the correct way that github-action works. It is the consequence of using Cypress Module API introduced in It is now documented in the README > Node.js section. I suggest to now close this issue as as far as I can see there is nothing which should be corrected in |
Thanks for the explanation @MikeMcC399 ! |
Hello, This issue start to happen again since, last Friday 5th of July. I'm following the workaround here That fixed it for now. |
Which version of webpack are you using? If you still need assistance, please open a new issue and post your full workflow and your |
Issue: Cypress does not pick up the NodeJS version set by another GH Action
Versions: Cypress 9.x
Steps to reproduce:
12
(which is used by default in the Cypress GH Action) and (b) execute any Cypress test.Prerequisites: (a) a GH repo and (b) a GH workflow
yml
config.Conclusions: Regardless of the NodeJS version set by
actions/setup-node@v2
Cypress still uses the default12
. This is working as expected with Cypress 8.x.Example: https://github.com/sergiubcn/cy-ci-node/runs/4467813743?check_suite_focus=true
https://github.com/sergiubcn/cy-ci-node/blob/master/.github/workflows/cicd.yml
Note: This does not reproduce locally if setting various NodeJS versions via
nvm use
.If it actually turns out to be an issue with Cypress I'll gladly move this ticket to that repo.
The text was updated successfully, but these errors were encountered: