-
Notifications
You must be signed in to change notification settings - Fork 860
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
Node.js version update to LTS (12) for pipeline tasks #2967
Comments
Bump. The current version fails with assert, and it's not supported by node team yet. See nodejs/node#34633 |
Note that the documentation of azure-pipelines-task-lib is indirectly claiming that node14 is supported: https://github.com/microsoft/azure-pipelines-task-lib/blob/master/node/docs/nodeEnvironment.md |
Given that Node.js 10 support ended on 30th April 2021, are there any plans to add Node.js 12 (maintenance LTS) or 14 (active LTS)? |
Node 6 is causing problems with the recently updated Root certificate of letsencrypt as well. See the issue(s) with Sonarqubes plugin: https://community.sonarsource.com/t/cert-has-expired-issue-on-sonarqube/25656/29 |
Or perhaps Node 16, now that "Active Support" for Node 14 ended today according to endoflife.date. |
Would really like to see this get updated so we can use Ed25519 ssh keys |
Just as a quick update - there are plans to introduce Node 14 execution handler and start updating tasks to this, but it could take some time due to wide and significant changes. |
Nice! Perhaps even Node 16, since "Active Support" for Node 14 ended last October? |
GitHub Action's equivalent change skipped Node 14 and went directly to Node 16: actions/runner#1439 |
There are currently 2 PRs open to add support for new versions of Node.js EDIT: The PR adding Node.js 18 support was abandoned as Node.js 18 requires glibc 2.28, but ubuntu 18.04 only provides glibc 2.271 Footnotes |
@anatolybolshakov I think this can be closed now that #3861 is merged |
This issue has had no activity in 180 days. Please comment if it is not actually stale |
Hi! Are there any plans to update Node version used for pipeline tasks execution to the current LTS (12)? We are working on CopyFilesOverSSH pipeline and faced with an issue that for Ed25519 key support we need to use at least Node 12 - for current version (Node6 or Node10) it is possible, but it requires much more efforts, so it would be great to have the latest version onboard.
The text was updated successfully, but these errors were encountered: