Update old version of publishing API to support platform-specific releases

[radeksimko]

The latest published version of ovsx (v0.5.0) supports platform-specific releases via ovsx --target flag.

However, the Registry running at open-vsx.org does not seem to support this.

The issue was discussed initially here:

• Publish newest cli to npm eclipse/openvsx#450 (comment)
• Publish newest cli to npm eclipse/openvsx#450 (comment)
• Publish newest cli to npm eclipse/openvsx#450 (comment)
• Infer publish target from package manifest & allow multiple --packagePath args eclipse/openvsx#461

At this point we are still blocked from publishing our extension to open-vsx.org unfortunately. The situation is worse in that I managed to publish a platform-specific extension which appears to be universal, hence appears broken for all users except for users of that single platform.

Could we get the API updated, please? 🙏🏻

[kineticsquid]

@radeksimko Do you want us to un-publish your extension until we get this sorted out?

@spoenemann @mbarbero I should know this but don't, what version are we running at open-vsx.org?

[radeksimko]

@kineticsquid If you could unpublish all versions above 2.20.0 (i.e. make 2.20.0 the latest available version) that would be amazing! 🙏🏻 2.20.0 is the last version which was universal, before we started publishing platform-specific ones.

https://open-vsx.org/extension/hashicorp/terraform

I should know this but don't, what version are we running at open-vsx.org?

Perhaps not related to this particular issue, but would it be useful to expose the version somewhere in footer, so that everyone can know?

[kineticsquid]

@radeksimko Done!

@spoenemann Thoughts on this enhancement request?

[spoenemann]

I'm not deep enough into that topic. @amvanbaren @jeanp413 @filiptronicek WDYT?

[amvanbaren]

eclipse/openvsx#21

It would be useful to check the server version in ovsx before executing a command, because the repository URL can vary by setting the -r parameter. It would also be useful for checking compatibility with an upstream registry.

[radeksimko]

@amvanbaren am I right the production version was now updated as part of #1094 , so publishing platform-specific extensions is now possible, or are there some other changes tracked anywhere that need to happen?

[amvanbaren]

@radeksimko Yes, publishing platform-specific extensions is now possible.

[radeksimko]

I'm assuming this was rolled back as part of the Friday outage? https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/1483

[filiptronicek]

@radeksimko yes indeed, this is not possible right now again :(

[lnicola]

Yes, publishing platform-specific extensions is now possible.

We (in rust-analyzer) have a CI action that tries to publish the extension each night, and it never worked. So maybe there are multiple issues at play.

[radeksimko]

Is there any updated plan on rolling out the new version? It looks like a number of extensions are essentially blocked by this

• Publish to Open VSX Registry wgsl-analyzer/wgsl-analyzer#28
• Add support for platform specific extensions muhammadsammy/free-vscode-csharp#39
• chore: publish to open-vsx vuejs/language-tools#1255
• Add OpenVSX publishing hashicorp/vscode-terraform#1064

[amvanbaren]

@radeksimko open-vsx.org now does support target specific extensions, but timeouts have been reported when publishing.
Improvements are on the way. I'm blocked by helpdesk issue #2104. I've added your comment and bumped the priority to high.

[lnicola]

but timeouts have been reported when publishing

Note that on our side it reverted to returning 500.

[pm4rcin]

@amvanbaren how's it going because the issue you mentioned on Eclipse's gitlab was closed?

[amvanbaren]

Hi @pm4rcin, the API supports platform-specific releases for a while now. I think the issue can be closed. @radeksimko Please re-open this issue if platform specific releases still don't work for you.