We currently publish a development VSIX to a GitHub pre-release on every push to master, but users cannot opt into automatic pre-release updates through the VS Code Marketplace.
We cannot simply publish the current version such as 3.0.0-rc.0: Marketplace pre-releases still require a plain major.minor.patch version and do not support SemVer pre-release identifiers.
I propose that we:
- define a Marketplace-compatible versioning scheme for 3.x pre-releases;
- regularly publish development builds with
vsce publish --pre-release;
- keep normal stable releases unchanged.
This would make testing upcoming 3.x releases much easier without requiring users to manually download and install VSIX files.
We currently publish a development VSIX to a GitHub pre-release on every push to
master, but users cannot opt into automatic pre-release updates through the VS Code Marketplace.We cannot simply publish the current version such as
3.0.0-rc.0: Marketplace pre-releases still require a plainmajor.minor.patchversion and do not support SemVer pre-release identifiers.I propose that we:
vsce publish --pre-release;This would make testing upcoming 3.x releases much easier without requiring users to manually download and install VSIX files.