Skip to content
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

download:plugins should respect Version #13686

Open
tsmaeder opened this issue May 6, 2024 · 0 comments
Open

download:plugins should respect Version #13686

tsmaeder opened this issue May 6, 2024 · 0 comments
Labels
builtins Issues related to VS Code builtin extensions open-vsx issues related to the open-vsx registry vscode issues related to VSCode compatibility

Comments

@tsmaeder
Copy link
Contributor

tsmaeder commented May 6, 2024

Feature Description:

Right now we are using the uri of an extension pack (https://open-vsx.org/api/eclipse-theia/builtin-extension-pack/1.83.1/file/eclipse-theia.builtin-extension-pack-1.83.1.vsix) to specify which built-ins we want to download. However, when we download the plugins in the built-in extension pack, we download whatever the newest compatible version of that plugin at open-vsx.org is at the time of the download. This might lead to a mix of versions and thus unpredictable builds and behavior.

We should be able to better control this. Ideas are:

  1. Don't use extension packs, use individual plugin uri's
  2. Allow to specify a version range for the plugin versions on the download uri
  3. Allow to specify a maximum API level required for the plugins in the extension pack.
@tsmaeder tsmaeder added vscode issues related to VSCode compatibility builtins Issues related to VS Code builtin extensions open-vsx issues related to the open-vsx registry labels May 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
builtins Issues related to VS Code builtin extensions open-vsx issues related to the open-vsx registry vscode issues related to VSCode compatibility
Projects
None yet
Development

No branches or pull requests

1 participant