Open
Description
This idea has probably been already discussed before but I didn't find the exact issue. @TylerLeonhardt and me discussed how VS Code supports stable/beta releases of extensions without the marketplace doing anything, and found this doable in practice:
- Extensions publish
- Publish a version 1.0, with engine set to
1.51
(note that there is no^
so we publish a version targeting VS Code Stable 1.51) - Publish a version 1.1 with engine set to
1.52-Insider
. This version will only work in 1.52 Insiders - Then publish a version 1.2 with engine set to
1.51
if there are important bug fixes need to ship to users on VS Code 1.51 - Continue publishing versions 1.x with engine
1.52-Insider
- Publish a version 1.0, with engine set to
- VS Code
- We fetch the last compatible version for current distro. For example, VS Code Insiders will always get the last version whose engine is set to
1.52-Insider
while Stable users will get the last one with engine1.51
- We fetch the last compatible version for current distro. For example, VS Code Insiders will always get the last version whose engine is set to
With above approach, extensions can use the same extension for different distro, which is helpful for testing proposed api. It's different from support beta version of extensions.