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 Nodejs to 22 #2619

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Upgrade Nodejs to 22 #2619

wants to merge 3 commits into from

Conversation

dchyun
Copy link
Contributor

@dchyun dchyun commented Dec 19, 2024

πŸ“Œ Summary

  • Shifted supported version of Node.js from 16* || >= 18 to >=18
  • Upgraded Node.js version of CI workflows from 20.x to the latest LTS of 22.x

πŸ› οΈ Detailed description

Removing support for Node.js 16 due to the following factors

πŸ”— External links

Jira ticket: HDS-4265


πŸ‘€ Component checklist

πŸ’¬ Please consider using conventional comments when reviewing this PR.

Copy link

vercel bot commented Dec 19, 2024

The latest updates on your projects. Learn more about Vercel for Git β†—οΈŽ

Name Status Preview Updated (UTC)
hds-showcase βœ… Ready (Inspect) Visit Preview Dec 19, 2024 5:11pm
hds-website βœ… Ready (Inspect) Visit Preview Dec 19, 2024 5:11pm

@@ -330,6 +330,6 @@
"dist"
],
"engines": {
"node": "16.* || >= 18"
"node": ">= 18"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@alex-ju I'm curious your opinion on this. Technically this should be considered a breaking change, but AFAICT we don't have any known consumers using Node 16. On the other hand, there is no real need for us to make this change either.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

According to the latest findings around the API our consumers are mostly concerned about the changes not affecting them, rather than following a rigid versioning policy. Based on this, and considering Ember dropped support for Node 16 in v5.11.0, so I'd say we can do it in a minor release too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants