Since it isn't possible to pin to a minor/patch version of an extension within Azure DevOps, it would be a good idea to release a major version of the current state of things, before we make too many more changes.
I would suggest releasing 0.3.0 which is upcoming, verify that everything is working as expected, and then release 1.0.0.
flcdrg
commented
4 years ago
Since it isn't possible to pin to a minor/patch version of an extension within Azure DevOps, it would be a good idea to release a major version of the current state of things, before we make too many more changes.
I would suggest releasing 0.3.0 which is upcoming, verify that everything is working as expected, and then release 1.0.0.