-
Notifications
You must be signed in to change notification settings - Fork 101
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
CircleCI test-deploy workflow uses end-of-life Node.js 16 #448
Comments
It seems that https://app.circleci.com/pipelines/github/cypress-io/circleci-orb is not currently being triggered. |
@MikeMcC399 Yes, I did notice this. I briefly looked at it but have no idea why.
|
@MikeMcC399 Figured it out with some help! #449 (comment) |
Thank you for taking a look at this. I can't be much help as I'm inexperienced with CircleCI and I don't have visibility into the CircleCI settings https://github.com/cypress-io/circleci-orb/settings either. |
Since
15 , this restricts Node.js to ^14.20.0 || ^16.13.0 || ^18.10.0 according to Angular > Version compatibility.
Angular
|
Did #449 close this issue @jennifer-shehane ? |
https://github.com/cypress-io/circleci-orb/blob/master/.circleci/test-deploy.yml still contains the following usage of the now unsupported Node.js circleci-orb/.circleci/test-deploy.yml Lines 24 to 26 in 6fe76b4
circleci-orb/.circleci/test-deploy.yml Lines 35 to 37 in 6fe76b4
circleci-orb/.circleci/test-deploy.yml Lines 46 to 48 in 6fe76b4
This issue therefore remains unaddressed. |
The CircleCI workflow .circleci/test-deploy.yml is configured to use the Docker container:
cypress/browsers:node-16.18.1-chrome-109.0.5414.74-1-ff-109.0-edge-109.0.1518.52-1
whereas the executor has been updated to
node-version: "20.6.0"
.Node.js
16
already reached end-of-life on Sep 11, 2023 and is no longer supported.(Runs are logged to https://app.circleci.com/pipelines/github/cypress-io/circleci-orb.)
Suggestion
Use a minimum Node.js
18.x
version compatible with the examples/angular-app version installed.The text was updated successfully, but these errors were encountered: