[Question]: UseNode@1 migration notes from NodeTool@0

[fowl2]

Task name

UseNode

Task version

1

Question

NodeTool@0 has recently been marked as deprecated:

This task is deprecated and will no longer receive updates. Please use UseNodeV1 as a replacement

The docs don't say what the difference is between it and UseNode@0, nor provide any guidance on how to update. The reasoning for the deprecation is apparently hidden inside a MSFT ADO link. :(

Doing the work myself, comparing the docs, it seems that the new task:

1. has renamed to versionSpec to version (yay churn)
2. no longer supports reading the version from a file (eg. .nvmrc)
3. no longer has mirror support

Overall it does not seem like a good replacement.

Am I missing something? Could we get some guidance?

Also, could we clarify what "will no longer receive updates" means? Does it mean that new Node versions will no longer be available going forward?

Thanks!

[snakefood3232]

I see you're concerned about the differences in UseNode@1, particularly its lack of support for reading versions from a file and mirror support. I'd handle this by creating a migration guide that addresses these differences and explores workarounds for maintaining functionalities like .nvmrc support. Additionally, I'll clarify what "no longer receive updates" means regarding NodeTool@0. I can have a PR up addressing these points within 3 days. I've navigated similar migrations in the past, ensuring seamless transitions for projects using deprecated tools.

[HamsterExAstris]

UseNode@1 is marked as "preview". So clarification on the support story would also be appreciated. (i.e. if we change the task as requested, does that mean Microsoft will no longer support our pipelines?)

[GlenAppleton]

Q: Why would the current task (even if not being supported) be removed from the ADO Market Place for classic pipelines, with no way to use the new (Preview) version in a new classic pipeline?

We're working on converting to YAML, but we have many legacy projects that still use classic pipelines and we need a way to support those.

[HamsterExAstris]

@GlenAppleton By default, tasks with no non-deprecated non-preview versions are hidden at the bottom. You have to expand that section, select the deprecated task, and then switch to the preview version.

[GlenAppleton]

@GlenAppleton By default, tasks with no non-deprecated non-preview versions are hidden at the bottom. You have to expand that section, select the deprecated task, and then switch to the preview version.

Thank you! This helped a lot. However, it's not obvious from the list of tasks, and the fact that searching the installed tasks can't find it. But again, thank you for letting me know how to find it.