cypress-io / circleci-orb

Install, cache and run Cypress.io tests on CircleCI with minimal configuration.

Home Page:https://circleci.com/orbs/registry/orb/cypress-io/cypress

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

CircleCI test-deploy workflow uses end-of-life Node.js 16

MikeMcC399 opened this issue · comments

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 Node.js 20 for the Docker containers, for example, using the latest available cypress/browsers:node-20.x Docker image from :

cypress/browsers:node-20.9.0-chrome-118.0.5993.88-1-ff-118.0.2-edge-118.0.2088.46-1

@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)

@jennifer-shehane

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

"@angular/cli": "~15.1.4",
is currently using Angular 15, this restricts Node.js to ^14.20.0 || ^16.13.0 || ^18.10.0 according to Angular > Version compatibility.

Angular 15 reaches end-of-life on May 18, 2024 so at some stage a migration to at least Angular 16 (supports Node.js ^16.14.0 || ^18.10.0) or preferably Angular 17 (supports Node.js ^18.13.0 || ^20.9.0) should be planned.

Did #449 close this issue @jennifer-shehane ?

@jordanpowell88

Did #449 close this issue?

https://github.com/cypress-io/circleci-orb/blob/master/.circleci/test-deploy.yml still contains the following usage of the now unsupported Node.js 16 version:

run-ct-tests-in-chrome:
docker:
- image: cypress/browsers:node-16.18.1-chrome-109.0.5414.74-1-ff-109.0-edge-109.0.1518.52-1

run-ct-tests-in-firefox:
docker:
- image: cypress/browsers:node-16.18.1-chrome-109.0.5414.74-1-ff-109.0-edge-109.0.1518.52-1

run-ct-tests-in-edge:
docker:
- image: cypress/browsers:node-16.18.1-chrome-109.0.5414.74-1-ff-109.0-edge-109.0.1518.52-1

This issue therefore remains unaddressed.