OctopusDeploy / OctoTFS

| Public | Octopus extensions for Azure DevOps, TFS, VSTS, and VSO
https://marketplace.visualstudio.com/items?itemName=octopusdeploy.octopus-deploy-build-release-tasks
Other
0 stars 41 forks source link

Node 6 execution handler warning in Azure DevOps #203

Closed older closed 2 years ago

older commented 2 years ago

Recently all tasks from Octopus Deploy started producing the following warning

[warning]This task uses Node 6 execution handler, which will be deprecated soon. If you are the developer of the task - please consider the migration guideline to Node 10 handler - https://aka.ms/migrateTaskNode10. If you are the user - feel free to reach out to the owners of this task to proceed on migration.

Currently I have this extension:

Installed version 4.2.492 (Latest)

tbolon commented 2 years ago

Also note that the warning has changed:

[warning]This task uses Node 6 execution handler, which will be removed March 31st 2022. If you are the developer of the task - please consider the migration guideline to Node 10 handler - https://aka.ms/migrateTaskNode10 (check this page also if you would like to disable Node 6 deprecation warnings). If you are the user - feel free to reach out to the owners of this task to proceed on migration.

The task will cease to work at the end of this month.

older commented 2 years ago

Now the warning seem to be gone. I don't see it in the logs any more, even so version of octopus extension has not changed: Version: 4.2.492

tbolon commented 2 years ago

image

Still receiving the error here.

johnsimons commented 2 years ago

Hi @tbolon and @older,

We are planning to release a new version of the tasks that run on Node10, keep an eye on https://github.com/OctopusDeploy/OctoTFS/pull/219

johnsimons commented 2 years ago

Now the warning seem to be gone. I don't see it in the logs any more, even so version of octopus extension has not changed: Version: 4.2.492

@older I am not sure why the error would be gone now, we haven't fixed that yet!

johnsimons commented 2 years ago

This is now fixed as part of https://github.com/OctopusDeploy/OctoTFS/pull/219

The release number is v4.2.559