Mutation Report Publisher failed to load since Release 1.2.0

[blcdb]

Environment
Azure Devops Server 2020 update 1.2
Mutation Report Publisher 1.2.0

Describe the bug
The mutation report fail to load since the update 1.2 of the task on an azure devops server 2020 update 1.2 on premise deployment.
When opening the tab, this url is called : http://{base_url}/DefaultCollection/{team_project_id}/_apis/build/builds/{build_id}/attachments/stryker-mutator.mutation-report
An error 400 occurs when accessing the report tab with the message : The requested REST API version of 7.2 is out of range for this server. The latest REST API version this server supports is 6.1.
This blocks the loading of the tab.

The publication seems to works just fine, it's just the tab's display that is impacted.

[rouke-broersma]

I didn't think this extension worked on azure devops server in the first place. I don't know if we can use a lower api version with a new sdk version.

[youssefboujlal]

Hello @rouke-broersma ,

Thank you for your contribution. I noticed that this release(commit : 994c763) introduces breaking changes due to the update of the azure-devops-extension-api from v2 to v4. To maintain compatibility for clients on Azure DevOps Server with API versions below 7.1, it's necessary to increment the major version.

Could you please proceed with updating the version to reflect these changes? This is crucial for ensuring a smooth experience for clients still on older API versions.

Thanks again for your contribution and understanding.

Best regards,

references :
Versioning guideline : https://www.conventionalcommits.org/en/v1.0.0/

[rouke-broersma]

@youssefboujlal there is no versioning for UI contributions as far as I know, so I'm not sure how you expect me to do this. The only thing I could do is apply a versioning constraint so the extension is no longer available for azure devops server.

[youssefboujlal]

@rouke-broersma In the information provided with the extension, it is specified that it is compatible with Azure DevOps Server. I believe that maintaining this compatibility is crucial to avoid impacting Azure DevOps Server users.

[rouke-broersma]

@youssefboujlal I would love to support Azure Devops Server if possible, but 1. I don't have a way to test compatibility and 2. I don't know how to maintain the compatibility while also avoiding vulnerable package versions.

If you have suggestions or can provide a pull request that fixes this issue for azure devops server I am happy to accept it. Until then I can't move forward with this.

[cartsp]

Our organisation has also been having this issue for sometime. Does anyone know any work arounds or a way to have an earlier version of the extension installed on Azure Devops?