search

JustusAdam / language-haskell

Highlighting support for the Haskell language in visual studio code.
https://marketplace.visualstudio.com/items/justusadam.language-haskell
BSD 3-Clause "New" or "Revised" License
95 stars 49 forks source link

Publish on open-vsx.org #171

Open lukel97 opened 4 years ago

lukel97 commented 4 years ago

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 commented 4 years ago

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

jankeromnes commented 4 years ago

@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.)

marcin-rzeznicki commented 3 years ago

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

filiptronicek commented 2 years ago

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

marcin-rzeznicki commented 2 years ago

Thanks @filiptronicek :rocket:

JustusAdam commented 2 years ago

@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?

filiptronicek commented 2 years ago

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.

re-xyr commented 2 years ago

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