feature: push to open-vsx.org

[lrstanley]

Currently, it looks like this extension is only pushed to the VSCode Marketplace, however this means that wrapped/custom vscode implementations are unable to utilize this extension without manually downloading and installing it. It would be nice if it could get added to https://open-vsx.org/, to allow things like https://github.com/coder/code-server to use it.

[anderseknert]

Oh, nice! Yeah, that definitely sounds like a good idea 👍

[glisha]

I don't see any CI scripts in the repo here, so I guess publishing to the MS marketplace is done manually?

If so and based on the frequency of new versions, the same can be done with the https://open-vsx.org/ so that the extension shows up in code-server extensions tab.

It would be nice for @tsandall or someone that he is comfortable with to do it so the same namespace can be in both.

The steps are:

1. Sign the Eclipse Foundation Open VSX Publisher Agreement - https://www.eclipse.org/legal/open-vsx-registry-faq/#faq-6
2. Publish the packages - https://github.com/eclipse/openvsx/wiki/Publishing-Extensions#how-to-publish-an-extension

There is also a Github Actions ready script that can be configured to publish to both marketplaces at the same time. https://github.com/open-vsx/publish-extensions

[ChristianKuehnel]

Hey @tsandall, let me know if you would be fine with automatic releases to both marketplaces and I'd offer my help in setting this up using the scripts linked in the previous post.

[anderseknert]

@ChristianKuehnel I've signed the various agreements and I'm looking into having it published. I'm not sure I understand namespaces though. Are we restricted to use the same namespace as the publisher field in the package.json file? That'd be "tsandall", but while Torin is still around (🙂), his handle is used as the publisher only because the VS Code marketplace won't allow it to be changed. Can we use open-policy-agent as our namespace when we publish this to Open VSX?