By declaring the extension able to run on the default node, ADO was detecting our task as being one that used node6, because that was technically available as a fallback. We've removed this, and the extension runs again with the node6 restriction enabled.
By declaring the extension able to run on the default
node, ADO was detecting our task as being one that used node6, because that was technically available as a fallback. We've removed this, and the extension runs again with the node6 restriction enabled.Closes #44