microsoft / azure-boards-estimate

MIT License
34 stars 24 forks source link

Unable to publish extension due to error : - Incompatible API version (5.1) #227

Closed jannuvi closed 1 year ago

jannuvi commented 1 year ago

We've just come across the same issue using the latest extension from the marketplace.

121

EstimateExt_error

Azure Instance Details: Azure DevOps Server 2019 (on premise) Version 17.143.28621.4

jannuvi commented 1 year ago

@AminTi - this page seems to suggest the 'supported' API version for 2019 is 5.0 - does this mean the extenstion doesn't work with Azure Devops Server 2019? https://learn.microsoft.com/en-us/azure/devops/integrate/concepts/rest-api-versioning?view=azure-devops

AminTi commented 1 year ago

Hi, it should work for 2019, I will check and get back to you.

jannuvi commented 1 year ago

@AminTi Any updates on the issue ?

AminTi commented 1 year ago

HI! I had to prioritize some other issues, but I will try to reproduce it as soon as possible.

abbottbd commented 1 year ago

IMHO it seems pretty simple. Azure Devops 2019 only supports API version 5.0 - look at the MSFT document in the link here: https://learn.microsoft.com/en-us/azure/devops/integrate/concepts/rest-api-versioning?view=azure-devops

The manifest for this extension says 'API vesion 5.1' hence Azure Devops Server 2019 blocks the install (5.1 > 5.0). Do you actually need anything that exists in API version 5.1 but doesn't exist also in API version 5.0?

jannuvi commented 1 year ago

IMHO it seems pretty simple. Azure Devops 2019 only supports API version 5.0 - look at the MSFT document in the link here: https://learn.microsoft.com/en-us/azure/devops/integrate/concepts/rest-api-versioning?view=azure-devops

The manifest for this extension says 'API vesion 5.1' hence Azure Devops Server 2019 blocks the install (5.1 > 5.0). Do you actually need anything that exists in API version 5.1 but doesn't exist also in API version 5.0?

@AminTi any updates on this query ?

AminTi commented 1 year ago

Hi, I just released an update now and test it on-prem 2019 it works as expected. let me know if you still have the same issue.