Tag Build task is dependent on Node version (1) that is end-of-life

[hlattanzio]

I'm getting this warning using the Tag Build task:

'Tag Build or Release' version 0 (tagBuildOrRelease@0) is dependent on a Node version (10) that is end-of-life. Contact the extension owner for an updated version of the task. Task maintainers should review Node upgrade guidance: https://aka.ms/node-runner-guidance

Is there an updated version? I don't see one...

Thank you

[aaron-champion]

Seeing the same. I think a number of tasks in the extension are still referencing Node10 version.

[dosekk]

I second this

[lachlann562]

This started appearing today for our on-prem agents.

[SenseiJoe]

Same here

[nuzolx]

For yaml pipeline: https://learn.microsoft.com/en-us/azure/devops/pipelines/build/build-tag?view=azure-devops&tabs=azure-devops-cli#filter-with-a-build-tag

[github-actions]

🤖 This is an automated response from Repo Assist.

Thanks for the reports! The tagBuildOrRelease@0 task currently uses the Node10 execution handler in its task.json, which Azure DevOps has deprecated.

Root cause: The task.json specifies Node10 execution. Microsoft is rolling out enforcement of Node runner deprecations for on-premise agents, hence the warning appearing even after previously being silent.

Short-term workarounds:

1. YAML log command (already mentioned above — great tip!): The simplest approach for build tagging is using an Azure Pipelines log command in a script step:

   - script: echo "##vso[build.addbuildtag]$(your-tag)"
     displayName: 'Tag build'

   This is native to Azure Pipelines and requires no external task.

2. AzureCLI for release tagging: For release pipeline tagging, az pipelines runs tag add works similarly.

Note on related work: There is an open draft PR #242 from Repo Assist that fixes a related case-sensitivity bug in the TagBuild task (where type: 'build' in lowercase would fail), but the Node 20 runtime upgrade is a separate concern tracked in the backlog.

Long-term fix: The task.json for tagBuildOrRelease@0 needs updating to use Node20_1. This is in Repo Assist's backlog for a future PR.

Thank you for your patience! 🙏

Generated by Repo Assist