-
Notifications
You must be signed in to change notification settings - Fork 500
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
[NodeJS18 Upgrade] Update support matrix for node18 #4303
Comments
hdhalter
added
1 - Backlog
Issue: The issue is unassigned or assigned but not started
and removed
untriaged
labels
Jun 13, 2023
@peterzhuamazon - Is this still on track for 2.10? |
Yes @hdhalter and we will need to change the matrix before 2.10 release. Thanks. |
71 tasks
peterzhuamazon
changed the title
Update support matrix for node18
[NodeJS18 Upgrade] Update support matrix for node18
Sep 6, 2023
peterzhuamazon
added
upcoming release
Don't merge until the version or feature is available
2 - In progress
Issue/PR: The issue or PR is in progress.
and removed
1 - Backlog
Issue: The issue is unassigned or assigned but not started
labels
Sep 6, 2023
1 task
hdhalter
added
3 - Done
Issue is done/complete
and removed
2 - In progress
Issue/PR: The issue or PR is in progress.
labels
Sep 7, 2023
peterzhuamazon
removed
upcoming release
Don't merge until the version or feature is available
v2.10.0
labels
Sep 12, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We are going to stay with node16 for 2.9, and plan to move to node18 for 2.10.
This would ensure us to have enough time for the upgrade.
As well as compensate the changes for multiple teams.
We can also start the Python3.9 upgrade process as Python3.7 is about to be eol by 2023/06/23.
Once we go to node18 in 2.10, the support matrix of our product will need to remove these OSes:
(Note: we still bundle node14 as fallback so technically above can still run, but 14 is eol and we do not officially support them anymore)
This also requires that the 2.x branch stays on 16.20.0 in .nvmrc, and have no node18 specific code committed until 2.9.0 is released to the public.
Infra will take care of the node18 upgrade once after 2.9.0.
Thanks.
Originally posted by @peterzhuamazon in opensearch-project/opensearch-build#1563 (comment)
The text was updated successfully, but these errors were encountered: