eyalbe4
commented
2 weeks ago Thank you for reporting this @johnpp143. Let's continue this duscussion in https://github.com/jfrog/jfrog-azure-devops-extension/issues/512 which was the trigger for that change.
Describe the bug
In the following commit, version support for older node has been updated to version 16. https://github.com/jfrog/jfrog-azure-devops-extension/pull/515/commits/fd7e26c987a5d1846da70b90c13b6d05a89a9d6d
This would cause potential failures for users using older node versions and older extension versions. We should keep support for node 10 as fallback? From microsoft guidelines https://learn.microsoft.com/en-us/azure/devops/extend/develop/add-build-task?view=azure-devops#q-how-can-i-upgrade-my-custom-task-to-the-latest-node
Current behavior
Extension failing with
[error]A supported task execution handler was not found. The task does not carry an implementation that is compatible with your current operating system 'Windows(X64)'. Contact the task author for more details.
for machines having older node version support.
Reproduction steps
No response
Expected behavior
No response
Azure DevOps extension name and version
New JFrog Azure Devops Extension
JFrog CLI version
2.54.0
Operating system type and version
Windows 21h2
JFrog Artifactory version (if relevant)
No response
JFrog Xray version (if relevant)
No response
JFrog Distribution version (if relevant)
No response