[Question]: Queries regarding Node20 support for SynapseWorkspace Deployment extension

[Bharath550-ms]

Task name

'Synapse workspace deployment

Task version

2.3.0

Environment type (Please select at least one enviroment where you face this issue)

• Self-Hosted
• Microsoft Hosted
• VMSS Pool
• Container

Azure DevOps Server type

dev.azure.com (formerly visualstudio.com)

Azure DevOps Server Version (if applicable)

No response

Operation system

Windows

Question

As a part of Node20 migration support documentation, we found that older node versions (6, 10 and 16) reached end-of-life. But there is a support if customers can use old node versions as a part of using custom extensions.
 
Details are provided here :
 
So, Do we have any ETA for the older node versions to get deprecated completely ? We are looking for a confirmation on whether our current ADO extension is going to be broken due to the retirement of the current Node.js version anytime soon.

Doc Links :

https://github.com/microsoft/azure-pipelines-tasks/blob/master/docs/migrateNode20.md
 
https://learn.microsoft.com/en-us/azure/devops/pipelines/agents/agents?view=azure-devops&tabs=yaml%2Cbrowser#node-runner-versions

https://learn.microsoft.com/en-us/azure/devops/extend/develop/add-build-task?view=azure-devops#q-how-can-i-upgrade-my-custom-task-to-the-latest-node

[imsharukh1994]

If you're already using Node.js 20 for your Azure DevOps (ADO) extension:

No immediate action is required. You're already using the supported version, and your extension will not be broken due to the deprecation of older Node.js versions (6, 10, and 16). The migration to Node 20 is exactly what Microsoft is pushing for, and as long as you're using it, your extension is safe.
If your extension is still using an older Node.js version (6, 10, or 16):

Upgrade your extension to Node.js 20 as soon as possible. Microsoft is transitioning all Azure DevOps tasks to Node.js 20, and older versions (6, 10, 16) will eventually stop being supported.
Follow the Node 20 migration documentation for details on how to migrate your custom tasks.
Test the Extension After Upgrade:

Once you've migrated to Node 20, thoroughly test your extension locally or in a staging environment to ensure everything works as expected.
Stay Informed:

Monitor the official Azure DevOps documentation and Azure DevOps Blog for any updates on deprecation timelines for older Node.js versions.

[Bharath550-ms]

@imsharukh1994, We are already upgrading our extension to support node.js 20, but there is some blocker in releasing the new version due to deployment blockers. So, Is there any deadline for upgrading the extension to support node.js 20 ? Does the extension becomes unusable if it doesn't support node.js 20 at any point of time ?

I don't find any official documentation and any updates in Azure DevOps Blog regarding deprecation timelines for extensions using older Node.js versions. If you have any information on exact deadlines, it would more useful.