Make current and previous versions download available

[HaGGi13]

Hello,

Current we are faced with issues to install the latest available package version (v4.16.13 - published 18.3.2024, 21:51:00) out of the marketplace.
So I wanted to download and install the package manually. Unfortunately, the lastest available version is from 2019.

Side note - here is the error we got:

Task definition visible rule 'getPRDetailsRepositoryId = ''' is invalid. It should be of format "A <validconditionhere> B" for Task with ID '7b0a5887-75c4-4ade-a915-f92a93c934cb'.

This brought me to the fact to suggest, to make all on marketplace published versions available to download via the GitHub page like other extensions do.

If this is already the case and I just didn't found it, I am super sorry and please to get pointed to.
In this case, it should be somewhere referenced to, to make it more obvious.

Thank you in advance and I am happy for any reaction on this.

Chris

[rfennell]

From the GUID I assume the task you are using is the XplatRelease notes, I ask as there are a number of them in this repository, and that is the reason why up to now I have not added VSIX packages as releases in the repo. I felt the different packages, with different release numbers in a single repo would be confusing if published as Git releases

So what I have done is make the Azure DevOps instance where I build and test the extensions public, and you can download the VSIX packages from retained pipelines e.g. Xplat release notes public builds

With hindsight I think put each extension in it's own repo would have been a better choice, maybe a change I should make, as it would help address your issue, and also make Dependabot usage easier (at present it generates some nasty PRs to resolve)

[HaGGi13]

Hi @rfennell, thanks a lot for your answer.

I see, I didn't realize before that you were using a mono repo approach. Yes, that makes it difficult to have different versions for each of the components it contains.
Indeed it would be easier to version each component if it would be located in its own repository. By doing so, you could use Git Actions to build and publish your packages with specific versions and adding the version as Git tag to the history.

Regards my initial question.
Thanks for sharing the pipeline link. I downloaded the package and tried to install it, but unfortunately I got the same error.

I'll search in the issues if something similar was already reported somewhen.

Thank you.