This PR is not ready to be merged, it is just a starting point to help contributors start.
The Node 16 migration guide is created keeping in mind that the in-the-box ADO tasks were already migrated to Node 10. In order to ensure smooth migration to Node 16, we need to ensure that the task can be run using a Node 10 handler as well. Please refer to the following guide for the same:
https://github.com/microsoft/azure-pipelines-tasks/blob/master/docs/migrateNode10.md
Since vsts-task-lib is deprecated, it should be replaced by azure-pipelines-task-lib. Also since typings is deprecated, I believe the typings.json file should be removed and @types packages should be used. It can be done by adding @types packages to package.json dependencies.
Please be sure to retest all tasks on node 10 and16 thoroughly
Reviewers and contributors, please follow the migration to node16 guide we have for in-the-box ADO tasks: https://github.com/microsoft/azure-pipelines-tasks/blob/master/docs/migrateNode16.md
This PR is not ready to be merged, it is just a starting point to help contributors start.
The Node 16 migration guide is created keeping in mind that the in-the-box ADO tasks were already migrated to Node 10. In order to ensure smooth migration to Node 16, we need to ensure that the task can be run using a Node 10 handler as well. Please refer to the following guide for the same: https://github.com/microsoft/azure-pipelines-tasks/blob/master/docs/migrateNode10.md
Since vsts-task-lib is deprecated, it should be replaced by azure-pipelines-task-lib. Also since typings is deprecated, I believe the typings.json file should be removed and @types packages should be used. It can be done by adding @types packages to package.json dependencies.
Please be sure to retest all tasks on node 10 and16 thoroughly