Include VSIX file in each GitHub Release
See original GitHub issueAs in most of microsoft/vscode-*
GitHub repos, it is a good practice to include the respective .vsix file in it. For example, microsoft/vscode-python does exactly that.
Why? Because it saves (tons of) time if someone wants to install an old version of the extension and test something. Also, due to backward compatibility with VSCode, installing an old version of the extension is desired sometimes.
This is something that maybe requires 2-3 hours of “doing time”, and there’s the potential of many people benefiting from it.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:7 (5 by maintainers)
Top Results From Across the Web
include .vsix on each release · Issue #519 · spring-projects/sts4
From what I understood it would be good to include the vsix files in the GitHub release, which I create manually every time...
Read more >Publish vsix files in the github releases, not only source code
I'm looking for the vsix file for release 2022.6.3, but cannot seem to find it anywhere. In the releases here on github, you...
Read more >Getting Started with the VSIX Project Template - GitHub
Select File > New > Project. In the search box, type "vsix" and select either the C# or Visual Basic version of VSIX...
Read more >VSIX Publisher · Actions · GitHub Marketplace
vsixmanifest file. Solution: Make sure that PackageManifest/Installation/InstallationTarget@Version is a range with both ends defined explicitly. Example of ...
Read more >Create a local release with .vsix file and publish from that #408
Yes, but then the build of the extension including things like bumping ... Create a local release with .vsix file and publish from...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It’s this one 2021.3.600686576 | 26/02/2021 | Download
Closing in favor of the following: