Publish chrischinchilla.vscode-pandoc to Open VSX

[goyalyashpal]

Hi!
do u have any plans to publish ur extension on open-vsx??
See this for more details: chrischinchilla.vscode-pandoc
Thanks!

[goyalyashpal]

pinging @ChrisChinchilla 😃

[ChrisChinchilla]

@yashpalgoyal1304 I didn't have any plans until now as as I had never heard of it, but I can take a look when I get a moment.

[goyalyashpal]

never heard of it

TL;DR: VSCodium (FOSS build of proprietary VSCode) and other derivations use open-vsx for extensions as these can't use the MS' marketplace due to T&C limitations

when I get a moment.

yeah sure :)

[goyalyashpal]

Dear extension author,
Please publish this extension to the Open VSX marketplace.

Context

Unfortunately, as Microsoft prohibits usages of the Microsoft marketplace by any other products or redistribution of .vsix files from it, in order to use VS Code extensions in non-Microsoft products, we kindly ask that you take ownership of the VS Code extension namespace in Open VSX and publish this extension on Open VSX.

What is Open VSX? Why does it exist?

Open VSX 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.

You can read on about Open VSX at the Eclipse Foundation's Open VSX FAQ.

How can you publish to Open VSX?

The docs to publish an extension can be found here. This process is straightforward and shouldn't take too long. Essentially, you need an authentication token and to execute the ovsx publish command to publish your extension. There's also a doc explaining the whole process with an example GitHub Action workflow.

[ChrisChinchilla]

@goyalyashpal I thought this was already working, but recently discovered that none of my extensions were publishing on the automated jobs I created. Now there are again! 🥳