Skip to content
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

Upgrade Node to 20 LTS #964

Closed
ken-mellem opened this issue Apr 18, 2024 · 1 comment · Fixed by #981, equinor/fusion-workspace#608 or equinor/lighthouse-client#1806
Closed

Upgrade Node to 20 LTS #964

ken-mellem opened this issue Apr 18, 2024 · 1 comment · Fixed by #981, equinor/fusion-workspace#608 or equinor/lighthouse-client#1806
Assignees

Comments

@ken-mellem
Copy link
Contributor

ken-mellem commented Apr 18, 2024

Upgrading node to 20 and pnpm to 9

This was linked to pull requests Apr 24, 2024
@ken-mellem
Copy link
Contributor Author

** Suggested AI description **

Description

Currently, our project is running on an older version of Node.js which is approaching its end-of-life date. To ensure continued long-term support, security updates, and performance improvements, we need to upgrade our Node.js runtime environment to the latest Long Term Support (LTS) version, which is Node 20 LTS.

Tasks

  • Verify that all project dependencies are compatible with Node 20 LTS.
  • Update the Node version and any Docker configurations.
  • Update the CI/CD pipeline to use the new Node 20 LTS version.
  • Perform a full regression test on the staging environment after the upgrade.
  • Monitor performance and error logs closely following the deployment to production.

Acceptance Criteria:

  • The application builds and runs successfully on Node 20 LTS without any errors.
  • All tests pass and the application behaves as expected.
  • No significant performance regressions are observed.
  • The CI/CD pipeline operates without issues using the updated Node version.

Note

We should also update the project's documentation to reflect the change in the Node.js version requirement. This upgrade should be scheduled during a low-traffic period to minimize potential impacts on users.

@Gustav-Eikaas Gustav-Eikaas linked a pull request Apr 24, 2024 that will close this issue
@Gustav-Eikaas Gustav-Eikaas self-assigned this Apr 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants