-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[engsys] update platform matrix for node 14 deprecation #27302
Conversation
A few other matrices where 14.x is used:
azure-sdk-for-js/sdk/communication/communication-phone-numbers/phone-numbers-livetest-matrix.json Line 24 in 77b3098
|
API change check API changes are not detected in this pull request. |
The keyvault failure looks unrelated since it's a recorder issue in secrets and I didn't change the platform configuration for it. I think I'm going to go ahead and merge to get this in, but /cc @timovv for awareness, so he might disparage me for my sins if I am regressing anything |
/check-enforcer override |
[engsys] update platform matrix for node 14 deprecation (Azure#27302) Update the CI matrix so we are no longer testing on Node 14 as it has reached the end of our EOL + 6 months policy. For coverage and browser legs I bumped it to use the current LTS (18) rather than 16 which is EOL, since most customers are not expected to be using an out of support runtime.
[engsys] update platform matrix for node 14 deprecation (#27302) Update the CI matrix so we are no longer testing on Node 14 as it has reached the end of our EOL + 6 months policy. For coverage and browser legs I bumped it to use the current LTS (18) rather than 16 which is EOL, since most customers are not expected to be using an out of support runtime. Co-authored-by: Jeff Fisher <[email protected]>
Describe the problem that is addressed by this PR
Update the CI matrix so we are no longer testing on Node 14 as it has reached the end of our EOL + 6 months policy.
For coverage and browser legs I bumped it to use the current LTS (18) rather than 16 which is EOL, since most customers are not expected to be using an out of support runtime.