Dart-code: Automate VSIX generation + publishing to VS Code + open-VSX for stable releases
Description
Are there any plans on releasing the extension as a .vsix file?
I noticed on the releases page of the repository that the source is released for a given tag but was wondering if it'd be possible to also include the .vsix as part of the release.
There is the odd .visx occasionally released: https://github.com/Dart-Code/Dart-Code/releases/download/v2.8.0-beta.1/dart-code-3.8.0-beta.1.vsix
The reason I ask is to be able to consume the extension in Theia (which supports VS Code extensions), and namely our Dart docker image.
The workaround at the moment is to fork the repository, perform the releases ourselves in .vsix format) and consume those.
Additional Info
vince-fugnitto
All 5 comments
The reason stable releases don't have them is that I typically didn't generate them (I just publish using vsce publish), but for beta releases they have to be installed manually, so the vsix is required.
The easiest way to get the vsix for the latest version is the Download extension button on the VS Code marketplace. Would this work well enough for you?
DanTup
on 12 Feb 2020
The easiest way to get the vsix for the latest version is the Download extension button on the VS Code marketplace. Would this work well enough for you?
Thank you for the prompt reply! Unfortunately, we cannot directly use or access the marketplace as it does not comply with their terms of use, mainly the fact that:
"Marketplace Offerings are intended for use only with Visual Studio Products and Services and you may only install and use Marketplace Offerings with Visual Studio Products and Services. "
For the moment, we have been consuming VS Code extensions from their respective repository's GitHub releases page as .vsix files, until we complete development of an open-source vsx registry. This will allow other applications (such as those based on Theia), to also consume VS Code extensions, and in turn bring more users to extensions.
vince-fugnitto
on 12 Feb 2020
Ah, fair enough! I've attached the v3.8.1 vsix files to the corresponding release pages. I'll try to remember to add them for future versions too, but feel free to ping me if I forget. Maybe at some point I can automate this better (I'd like to do this for dev builds anyway to avoid having to build manually for people wanting to try out fixes).
DanTup
on 12 Feb 2020
Ah, fair enough! I've attached the v3.8.1 vsix files to the corresponding release pages. I'll try to remember to add them for future versions too, but feel free to ping me if I forget. Maybe at some point I can automate this better (I'd like to do this for dev builds anyway to avoid having to build manually for people wanting to try out fixes).
Wow thank you so much! I really appreciate it! 馃憤
vince-fugnitto
on 12 Feb 2020
I'll re-purpose this issue for providing these more reliably. Thanks!
DanTup
on 12 Feb 2020
Related issues
mayorbyrne
路
5Comments
shamrin
路
5Comments
FeimiSzy
路
4Comments
ifredom
路
3Comments
lukepighetti
路
4Comments
Most helpful comment
Ah, fair enough! I've attached the v3.8.1 vsix files to the corresponding release pages. I'll try to remember to add them for future versions too, but feel free to ping me if I forget. Maybe at some point I can automate this better (I'd like to do this for dev builds anyway to avoid having to build manually for people wanting to try out fixes).