-
Notifications
You must be signed in to change notification settings - Fork 233
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
Outdated extensions #91
Comments
Good catch! Many thanks @acim for reporting these problems.
The namespace
The namespace
The namespace
*Publishing to https://open-vsx.org should be as simple as just running |
I manually pushed https://open-vsx.org/extension/redhat/vscode-yaml/0.9.1 (cc @JPinkney) |
Awesome, many thanks @fbricon! 💯 |
Ping @dbaeumer @fiveisprime |
Ok, given that In the interest of time, we will temporarily resume publishing @fiveisprime please let us know when you would like to take over the publishing of your extension, and we will be more than happy to help your team set it up and hand over the publishing. EDIT: New version is published: https://open-vsx.org/extension/ms-azuretools/vscode-docker |
@spoenemann Now that a fixed |
Done. |
We've now resumed auto-publishing of the other two extensions. Everything should be up-to-date again pretty soon. |
eslint in https://open-vsx.org/vscode/gallery is version 2.1.3 while the latest tag in https://github.com/microsoft/vscode-eslint/tags i 2.1.9.
Same is for the following extensions:
ms-azuretools.vscode-docker 1.0.0 -> 1.4.1
redhat.vscode-yaml 0.8.0 -> 0.9.1
The text was updated successfully, but these errors were encountered: