When an extension declares 2 contributions, say vsts-msbuild-helper-task-v0 and vsts-msbuild-helper-task-v1 and each of these point to a task.json that has the same name and id, but 2 different major versions, only the lowest major version will show up in Azure DevOps.
This validation catches that case.
Fixed by: #541
When an extension declares 2 contributions, say
vsts-msbuild-helper-task-v0andvsts-msbuild-helper-task-v1and each of these point to a task.json that has the samenameandid, but 2 different major versions, only the lowest major version will show up in Azure DevOps.This validation catches that case.
Fixed by: #541