-
Notifications
You must be signed in to change notification settings - Fork 293
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
Publish the VSIX files in the release #5582
Comments
That list (as of right now) has every version in it. |
Thanks for the screen shot of the list. It helped me to download the desired version. However, note that I am using VSCode in an environment with no internet connection at all so that I am forced to download the VSIX files manually and transfer them to that environment to install them offline. Thus, the "Install another version..." entry is disabled in my VSCode. |
Unfortunately, no, this is not the case. I have the same problem as the original poster @oli-arborum His system, like mine, is not directly connected to the Internet. The most recent versions of the extension (the only ones available with downloadable .vsix files) will not install in my version of VSCode, which cannot be changed for compatibility reasons. So there is no extension installed from which to get a dropdown with previous versions. Even if there was an extension installed, it could not load other versions since it cannot access the Internet. |
We have exactly the same issues in our environment: We use an older version of VSCode for compatibilty reasons in an offline environment and need to install the Jupyter extension because the Python extension requires it since version 2020.11. @stanmartin1 To download an arbitrary version of the Jupyter extension use the following URL: |
Thank you! this got me running. |
You're welcome! =) |
BTW, while hacking the URL is a cool workaround, it would still be best if the dev team could just include the .vsix file under the list of released artifacts, alongside the source. |
Yes, I second that proposal. |
We'll be discussing this in triage. There's a reason why it's not there at the moment. Mostly to do with licensing. I believe the license says the VSIX has to be acquired from the marketplace but I'm not a lawyer so not sure what the ramifications of sticking it in github releases is. If we can't put it on the github page, we'll log a bug with the marketplace team to make all versions available. We already have an issue against them to make it obvious which VS code the items in the marketplace work against. |
@rchiodo Just FYI - I looked into the six "most trending" extensions on the marketplace and their related GitHub release pages:
Do you notice anything? ;-) |
Hello, I tried the method mentionned here :
But doing the command
Got me an error message : Anyone found a way around this error ? |
Closing this issue, as we already have a way to get the release on the marketplace and some of the other partner teams too do not publish VSIX in the github release just as we do not
If this is still an issue please file an issue on VS Code |
Currently, it is impossible to retrieve old releases of this extension.
Reason: Neither the VSIX files are published in the releases (like in the Python Extension on https://github.com/microsoft/vscode-python/releases) nor the complete version string (e.g. "2021.6.755784270" for the latest release) is made available (also like it is done in the Python Extension) in order to be able to fetch the VSIX via the URL https://marketplace.visualstudio.com/_apis/public/gallery/publishers/ms-toolsai/vsextensions/jupyter/$VERSION/vspackage
Reason for request: There exist environments where a) a certain fixed version of VSCode is enforced or required and b) no direct internet connection from VSCode (to download extensions) is possible. If the used VSCode version is incompatible with the latest extension release, it is required to load a compatible (old) one manually.
If you see any chance where/how to get the Jupyter Extension version 2020.12 please give me an update on that.
The text was updated successfully, but these errors were encountered: