language-haskell icon indicating copy to clipboard operation
language-haskell copied to clipboard

Publish on open-vsx.org

Open lukel97 opened this issue 4 years ago • 8 comments

Hi, we're trying to upload the vscode-haskell extension to open-vsx.org here: https://github.com/haskell/vscode-haskell/issues/250, but we have a dependency in our package.json on this marvellous extension. Would it be possible to upload this to open-vsx.org as well? Since it seems like extensions can't be uploaded until all their dependencies are also uploaded

lukel97 avatar Aug 11 '20 16:08 lukel97

We've been following this guide to publish the extension: https://github.com/eclipse/openvsx/wiki/Publishing-Extensions#1-create-an-access-token

lukel97 avatar Aug 11 '20 16:08 lukel97

@bubba I would suggest keeping this feature request open.

As a quickfix, we are happy to add extensions to our auto-publishing CI in https://github.com/open-vsx/publish-extensions, but it's quite basic and bears the risk of not publishing exactly when/how/what is desired. So in general it's always better if maintainers take control of when/how/what they publish to OpenVSX. (And it's usually as easy as adding the single command npx ovsx publish to an existing Microsoft Marketplace publishing script.)

jankeromnes avatar Aug 19 '20 12:08 jankeromnes

3.4.0 seems not to have been published to OpenVSX still - pinging

marcin-rzeznicki avatar May 05 '21 19:05 marcin-rzeznicki

3.4.0 seems not to have been published to OpenVSX still - pinging

That is correct indeed, the publishing script in the https://github.com/open-vsx/publish-extensions repository is having some issues. In the meantime, I have created a doc describing the process on publishing, and I believe it should be pretty straight forward. I would love to help out!

cc @JustusAdam

filiptronicek avatar Mar 14 '22 21:03 filiptronicek

Thanks @filiptronicek :rocket:

marcin-rzeznicki avatar Mar 15 '22 11:03 marcin-rzeznicki

@bubba I would suggest keeping this feature request open.

As a quickfix, we are happy to add extensions to our auto-publishing CI in https://github.com/open-vsx/publish-extensions, but it's quite basic and bears the risk of not publishing exactly when/how/what is desired. So in general it's always better if maintainers take control of when/how/what they publish to OpenVSX. (And it's usually as easy as adding the single command npx ovsx publish to an existing Microsoft Marketplace publishing script.)

Since there were some other issues with my not-yet-automated publishing recently I might spend some time to do that and I'd be happy to add the mentioned publishing command as well. Are there access control stuff I'd have to take care of to get that set up now?

JustusAdam avatar Mar 16 '22 14:03 JustusAdam

I'd be happy to add the mentioned publishing command as well.

Great!

Are there access control stuff I'd have to take care of to get that set up now?

This boils down to creating an account on open-vsx.org and getting a personal access token. This is described in the step one of the aforementioned doc, linking to Publishing Extensions , where only the steps 1-4 are important for now. The rest happens in the CI pipeline itself.

filiptronicek avatar Mar 16 '22 19:03 filiptronicek

There is currently a v3.6.0 on Open VSX, but it is broken (#212). How could we fix this?

re-xyr avatar Apr 27 '22 01:04 re-xyr