FR: please co-publish on Open VSX Registry

[GitMensch]

The Open VSX Registry currently only has the AHK Plus extension published by its author (so that was at least maintained 2 years ago).
Open VSX Registry is the default extension provider endpoint for the free build of vscode VSCodium and Eclipse Theia. It would be nice to have this extension be directly published to a free vsix repository instead of only the Microsoft Marketplace with its restrictions.

Details on the publishing can be found at https://github.com/eclipse/openvsx/wiki/Publishing-Extensions, which also drops a link to https://github.com/HaaLeo/publish-vscode-extension#readme - a GitHub action that can publish to both marketplaces (if you want to automate it like "just create a release and get it published"), but that's optional.

[mark-wiemer]

Awesome, thanks for the resources. This was brought to my attention a while back, but I hadn't heard much in a while. Definitely want to support Codium. If this is easy, expect it this week. For now you can download the vsix from the releases tab of the repo

[mark-wiemer]

For reference: automated publishing guide

[mark-wiemer]

I am not alone in my token frustration: microsoft/vsmarketplace#161

[GitMensch]

Just out of interest: Does it get any better when using https://github.com/HaaLeo/publish-vscode-extension#readme for the automated publishing or is getting that token in a working state the main issue?

[mark-wiemer]

I would split this work into two categories:

1. First-time setup (creating accounts, creating tokens, registering namespaces, publishing app for the first time)
2. Recurring work (setting up workflows to publish automatically, streamlining those workflows)

On count 1, Visual Studio Marketplace has been a nightmare, where Open VSX has been a relatively normal experience, much closer to "just working".

On count 2, the automated publishing GitHub action you shared will make my life easier. It'd be nice if git / GitHub made it easier to generate tags, attach releases to them, and extract the titles and descriptions from Changelog.md, but I'll survive :)

I've almost got https://github.com/mark-wiemer/vscode-helloworld set up :)

[mark-wiemer]

See EclipseFdn/open-vsx.org#1114

[mark-wiemer]

Published HelloWorld on Open VSX :) https://open-vsx.org/extension/mark-wiemer/helloworld-2022

[mark-wiemer]

mark-wiemer/hello-vscode-extension#38

[GitMensch]

That's a useful repo to point to - thanks!

[GitMensch]

It'd be nice if git / GitHub made it easier to generate tags, attach releases to them, and extract the titles and descriptions from Changelog.md, but I'll survive :)

I see you've partially tackled this but you may want to have a look at a "full setup" (much more complicated as it - at least when looking the last time - tries to also create the Changelog/NEWS, not "just take it", but the simplified version may be what you aim for) westes/flex#480

[mark-wiemer]

Created #156 for that fancier work 😄

[mark-wiemer]

Unfortunately due to my frantic fix for #153, the repo is in a bad state in terms of automatic deployments. First priority is now "re-deploy 2.8.3 as 2.8.5 from main with necessary bugfixes", which will probably take a bit. I'm on vacation next week, so don't expect this until July 18 at the earliest. Sorry for the delay :(

[GitMensch]

I'm not in a hurry 😄, mainly got here by your deprecation post...

[mark-wiemer]

@GitMensch published 2.8.5 manually :)

AHK++ on Open VSX

[GitMensch]

The 2.8.5. release is missing here - do you mind creating it from the same source set?
I think this issue can be closed, because for everything else there is #122.

[mark-wiemer]

I'm not sure what you mean, I'm seeing it at the link I provided. Can you add some more details?

[GitMensch]

I'm not sure what you mean, I'm seeing it at the link I provided. Can you add some more details?

Open VSX is fine - and therefore the issue can be closed; but on GH releases there is only a 2.8.5 pre-release so far.

[mark-wiemer]

Ah, yes, I'd like to leave it that way. In all honesty, I should've just published 2.8.4 on OVSX, but it's too late. I don't think I can unpublish 2.8.5. My mistake.

I'm assuming OVSX is much smaller than Visual Studio Marketplace, and I'm confident enough in the release that 2.8.5 won't be as terrible as 2.8.3

If something is wrong, please let me know right away.

But I'm still not comfortable saying 2.8.5 is ready for general availability on VS Marketplace or GitHub. I'd like to give it a week total in pre-release mode before I move it to a regular release, if that's OK.

[GitMensch]

Sure. Still closing this as solve now :-)