You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
Describe the bug
In the following commit, version support for older node has been updated to version 16.
fd7e26c
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
The text was updated successfully, but these errors were encountered: