You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
VSCodium (the VSCode flavor without proprietary license restrictions) started using a libre registry of plugins to ensure independence from Microsoft telemetry support and marketplace sole control. This is called OpenVSX and is developed by the Eclipse Foundation.
This is a request for the maintainer of this plugin to add a GitHub action to release this extension on OpenVSX too. It requires registering an account, importing the secret token, and then adding the corresponding GitHub action to CI. See https://github.com/HaaLeo/publish-vscode-extension#readme
The text was updated successfully, but these errors were encountered:
We decided to remove this extension from the https://github.com/open-vsx/publish-extensions repository, since it has not had any activity for a while and we try to make the list of published extensions shorter.
This means that new versions of the extension will not be available on the OpenVSX registry, but feel free to enable automatic publishing yourselves, we made a pretty easy guide in our repo [1].
What is OpenVSX?
OpenVSX is a vendor neutral alternative to the MS marketplace used by most other derivatives of VS Code like VSCodium, Gitpod, OpenVSCode, Theia based IDEs, and so on.
VSCodium (the VSCode flavor without proprietary license restrictions) started using a libre registry of plugins to ensure independence from Microsoft telemetry support and marketplace sole control. This is called OpenVSX and is developed by the Eclipse Foundation.
This is a request for the maintainer of this plugin to add a GitHub action to release this extension on OpenVSX too. It requires registering an account, importing the secret token, and then adding the corresponding GitHub action to CI. See https://github.com/HaaLeo/publish-vscode-extension#readme
The text was updated successfully, but these errors were encountered: