Vscode-jest: [Feature Request?] Publish to the Open-VSX registry

[KartikSoneji]

Can this extension be published to the Open VSX registry as well?

Open VSX registry: https://open-vsx.org/
How to Publish an Extension: https://github.com/eclipse/openvsx/wiki/Publishing-Extensions

[jankeromnes]

Great idea! Friendly ping @orta 😇 🙏

[orta]

Ah yeah, sorry - I'm not actively maintaining this (other folks are) but if it needs me saying this is a good idea, then this is a good idea 👍🏻

[jankeromnes]

Awesome, thanks @orta! (Note: I asked you because you've also published svelte.svelte-vscode and svelte.svelte-vscode-nightly to OpenVSX -- many thanks for that! 💯)

@connectdotz or @stephtr would you be interested in publishing vscode-jest to OpenVSX? This would allow users from VSCodium, Gitpod, Theia, etc. to also use it. (Let me know if I can help!)

[connectdotz]

sorry slow to respond, yes we should publish there, I will try to do it this weekend

[connectdotz]

@orta this package is published under publisher = "Orta", which will also be the namespace in open-vsx. For security reason, we should claim the ownership of the namespace. But I wasn't sure if you have any other repo under "Orta"...

We should probably rename the publisher to jest-community at some point, what do you think? However, doing so in vscode is sort of tricky, especially given our install base. I see a few approaches and would like you to weight in:

1. hold off open-vsx publication until we rename the publisher in vscode
2. if you don't have any other packages under Orta namespace, we can claim and publish as "Orta" in open-vsx for now and change it to the new namespace later.
3. you can claim "Orta" namespace, grant us permission, either you or us can then publish under Orta. We can change to new namespace later.

[orta]

I have a bunch of extensions, so I can't really rename my vscode org.

I can claim the open namespace and put a token in the secret vault for this repo, then a deploy can automatically happen from here via a GH action?

[connectdotz]

I can claim the open namespace and put a token in the secret vault for this repo, then a deploy can automatically happen from here via a GH action?

It makes sense for you to claim the namespace.

However, we have not been using GH action in this repo yet, not that we can not set it up, just that it is not the current procedure... (Personally I prefer manual publication so we can better control the timing and quality)

If you add us as Contributors in open-vsx namespace (see here) then we can publish to it with our own token, I think it is more secure and accountable for each release publisher to use their own token anyway. Does that make sense?

[orta]

Perfect 👍🏻 doing it in https://github.com/eclipse/open-vsx.org/issues/122

[connectdotz]

@orta not sure if I missed it, are you able to add us as contributors?

[orta]

Alright, that's everything I think

[connectdotz]

Thanks, @orta.

ok, both 3.2.0 and 4.0.0-alpha.1 are published: https://open-vsx.org/extension/Orta/vscode-jest

@jankeromnes please let me know if there is any issue with it.

[jankeromnes]

That's awesome, many thanks @connectdotz and @orta! 💯 🙏

The uploaded extensions look good to me. 👍 (However, given that 4.0.0-alpha.1 is now the latest available version on OpenVSX, please note that this will be the default version that all users get when installing this extension in VSCodium, Gitpod, Theia, etc.)

[connectdotz]

hmm... is there a way to publish pre-release?

[jankeromnes]

hmm... is there a way to publish pre-release?

@connectdotz In theory, I think you can mark an extension as preview in its package.json, and then all marketplaces (e.g. OpenVSX) and tools (e.g. VSCodium) should always propose the latest non-preview version by default.

But I know that some extension authors prefer to publish with separate IDs and logos in order to avoid any potential confusion, like for example svelte.svelte-vscode vs svelte.svelte-vscode-nightly.