-
Notifications
You must be signed in to change notification settings - Fork 36
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
Re-publish v1.44.2 #41
Comments
Almost working - I think all that's needed now is for the originally published builtins v1.44.2 to be removed from the registry and to restart this GH workflow Current error: |
@spoenemann I think we can use the new GH action I recently added to re-publish 1.44.2, if someone can delete these vscode-builtins from open-vsx.org. |
Deleted 👍 |
…n to 1.39.1 Downgrade `vscode-builtin-markdown-language-features` built-in plug-in to 1.39.1. As 1.45.1 requires not implemented yet CustomEditor Plug-in API.
I am attempting to re-publish markdown-language-features v1.39.2: https://github.com/eclipse-theia/vscode-builtin-extensions/runs/1824045224?check_suite_focus=true If that works, I'll try with the full set of builtins v1.44.2, after |
another try: https://github.com/eclipse-theia/vscode-builtin-extensions/runs/1824119038?check_suite_focus=true |
Fixes #41 Signed-off-by: Marc Dumais <marc.dumais@ericsson.com>
Now trying for the set of vscode-builtins v1.44.2: |
@spoenemann Is it possible you missed removing one extension, publishing: /home/runner/work/vscode-builtin-extensions/vscode-builtin-extensions/dist/typescript-language-features-1.44.2.vsix |
Before encountering the error above, a good number of |
Fixes #41 Signed-off-by: Marc Dumais <marc.dumais@ericsson.com>
I changed the publish script slightly to permit continuying when an extension fails to publish. All but |
It seems that one slipped through. It's deleted now. |
I re-ran the workflow and |
Fixes #41 Signed-off-by: Marc Dumais <marc.dumais@ericsson.com>
upstream issue: eclipse-theia/theia#9014
This repo's CI is configured to publish with the
open-vsx
bot's credentials. I think we can tweak it to publish an arbitrary version, so long asopen-vsx.org
lets it happen.The text was updated successfully, but these errors were encountered: