This PR updates many dependencies to their latest version in order to support the Node16 execution handler. Most notable upgrades are azure-pipelines-task-lib and azure-pipelines-tool-lib which are crucial SDKs for custom task extensions. I had a look at the changelog for those two packages and didn't see anything concerning.
The Node10 execution handler must remain in the extension manifest until Azure stops supporting older build agents completely. They released v3.x for build agents earlier this year. While Microsoft-hosted build agents will automatically use the latest agent version, self-hosted build agents are opt-in at this time.
Thank you for contributing! Before submitting your PR, can you please confirm that you have done the following?
[ ] If you changed the values of the properties name, publisher, and galleryFlags in the vss-extension.json file, you have reverted them.
[ ] If you changed the values of the properties id, name, author, you have reverted them.
[ ] I have reverted any changes to the version number components in both vss-extension.json and task.json, OR I didn't change them.
This PR updates many dependencies to their latest version in order to support the Node16 execution handler. Most notable upgrades are
azure-pipelines-task-libandazure-pipelines-tool-libwhich are crucial SDKs for custom task extensions. I had a look at the changelog for those two packages and didn't see anything concerning.The
Node10execution handler must remain in the extension manifest until Azure stops supporting older build agents completely. They released v3.x for build agents earlier this year. While Microsoft-hosted build agents will automatically use the latest agent version, self-hosted build agents are opt-in at this time.Thank you for contributing! Before submitting your PR, can you please confirm that you have done the following?
name,publisher, andgalleryFlagsin thevss-extension.jsonfile, you have reverted them.id,name,author, you have reverted them.vss-extension.jsonandtask.json, OR I didn't change them.