New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support installing pre-release (alpha/beta/insiders) versions using VSIX #39024

Closed
sandy081 opened this Issue Nov 23, 2017 · 2 comments

Comments

Projects
None yet
3 participants
@sandy081
Member

sandy081 commented Nov 23, 2017

Currently, extension authors get their pre-release versions tested by the community using VSIXs. But VS Code does not support installing alpha/beta/insiders versions. This force authors to always use patch for pre-release versions.

By supporting alpha/beta/insiders versions, author can generate VSIXs like pub.extname-0.11.0-beta or pub.extname-0.11.0-beta-2. At the end, they can publish the release version pub.extname-0.11.0 and all users who are using pre-release versions will get the release update.

@sandy081

This comment has been minimized.

Show comment
Hide comment
@sandy081

sandy081 Nov 23, 2017

Member

To verify:

Step 1

  • Disable auto updating extensions
  • Publish an extension with version 0.10.0 that has a command which will print its current version when invoked.

Step 2

  • Compute a VSIX of the above extension with version 0.9.1 and prints 0.9.1 as its version
  • Install it and confirm it prints 0.9.1 as its version
  • Make sure the update to 0.10.0 is shown

Step 3

  • Compute a VSIX of the above extension with version 0.11.0-insiders and prints 0.11.0-insiders as its version
  • Install it and confirm it prints 0.11.0-insiders as its version

Step 4

  • Compute a VSIX of the above extension with version 0.11.0-insiders-2 and prints 0.11.0-insiders-2 as its version
  • Install it and confirm it prints 0.11.0-insiders-2 as its version

Step 5

  • Publish the extension with version 0.11.0 that prints 0.11.0 as its version
  • Make sure the update to 0.11.0 is shown
  • Install it and confirm it prints 0.11.0 as its version

Step 6

  • Try to install any older version and make sure it is installed correctly by checking the version

Step 7

  • Uninstall the extension and make sure extension is not shown in the viewlet
  • Quit and Start VS Code and open Extensions folder and make sure above extension folder does not exist.
Member

sandy081 commented Nov 23, 2017

To verify:

Step 1

  • Disable auto updating extensions
  • Publish an extension with version 0.10.0 that has a command which will print its current version when invoked.

Step 2

  • Compute a VSIX of the above extension with version 0.9.1 and prints 0.9.1 as its version
  • Install it and confirm it prints 0.9.1 as its version
  • Make sure the update to 0.10.0 is shown

Step 3

  • Compute a VSIX of the above extension with version 0.11.0-insiders and prints 0.11.0-insiders as its version
  • Install it and confirm it prints 0.11.0-insiders as its version

Step 4

  • Compute a VSIX of the above extension with version 0.11.0-insiders-2 and prints 0.11.0-insiders-2 as its version
  • Install it and confirm it prints 0.11.0-insiders-2 as its version

Step 5

  • Publish the extension with version 0.11.0 that prints 0.11.0 as its version
  • Make sure the update to 0.11.0 is shown
  • Install it and confirm it prints 0.11.0 as its version

Step 6

  • Try to install any older version and make sure it is installed correctly by checking the version

Step 7

  • Uninstall the extension and make sure extension is not shown in the viewlet
  • Quit and Start VS Code and open Extensions folder and make sure above extension folder does not exist.
@felixfbecker

This comment has been minimized.

Show comment
Hide comment
@felixfbecker

felixfbecker Dec 14, 2017

Contributor

I wish the marketplace just supported release channels (e.g. latest/stable, next/unstable/insiders, ...)

Contributor

felixfbecker commented Dec 14, 2017

I wish the marketplace just supported release channels (e.g. latest/stable, next/unstable/insiders, ...)

@vscodebot vscodebot bot locked and limited conversation to collaborators Jan 7, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.