-
Notifications
You must be signed in to change notification settings - Fork 51
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
Allow node 18, but not 18.12.1 #3485
Allow node 18, but not 18.12.1 #3485
Conversation
Signed-off-by: 1000TurquoisePogs <sgrady@rocketsoftware.com>
Signed-off-by: 1000TurquoisePogs <sgrady@rocketsoftware.com>
PAX build 3390 SUCCEEDED. |
Signed-off-by: 1000TurquoisePogs <sgrady@rocketsoftware.com>
Test workflow 2900 is started. |
PAX build 3391 SUCCEEDED. |
Test workflow 2901 is started. |
PAX build 3432 SUCCEEDED. |
Test workflow 2943 is started. |
PAX build 3445 SUCCEEDED. |
Test workflow 2954 is started. |
Signed-off-by: 1000TurquoisePogs <sgrady@rocketsoftware.com>
PAX build 3448 SUCCEEDED. |
Test workflow 2958 is started. |
Test workflow 2960 is started. |
This PR formally adds node v18 support to the servers.
There was nothing preventing 18 from running, but after testing we know that while node 18.14 works, node 18.12.1 on zos does not. Therefore, this PR really just adds a check to forbid 18.12.1, while letting all other versions run.
PR type
Relevant issues
Related to zowe/zlux#973
Documentation: zowe/docs-site#2976
Does this PR introduce a breaking change?