Please Publish to OpenVSX Marketplace 🙏

[trinitronx]

I'm submitting a

• publish / release request for OpenVSX

Your environment

Note that most environment details are unrelated to the issue except that I'm using Code - OSS which can only install extensions from OpenVSX.

Environment Details

• vscode-ruby-test-adapter version: 0.9.0
• Ruby version: any (tested on 3.0.6p216)
• VS Code version: 1.82.0

Full VSCode Details

• VS Code Full details - version: 1.82.0
  • Commit: microsoft/vscode@8b617bd
  • Date: 2023-09-11T16:30:45.959Z
  • Electron: 25.6.0
  • Chromium: 114.0.5735.134
  • Node.js: 18.15.0
  • V8: 11.4.183.23-electron.0
  • OS: Linux x64 6.5.3-1-MANJARO

• Operating System: Linux x64 6.5.3-1-MANJARO
• RSpec or Minitest version: rspec-core 3.12.2

Hi @connorshea !

I'm sure there are others who would love to use this extension but currently are encountering issue #56 due to the split between OpenVSX / VisualStudio Marketplace repos for OSS builds of VSCode.

In the past few years, many OSS Linux packagers of VSCode, VSCodium, (a.k.a. Code OSS) have moved to using OpenVSX extension Registry and had to disable Microsoft's Extensions Marketplace by default due to Microsoft's licensing restrictions.

So, in order for most Linux developers using stock OSS-packaged versions of VSCode to find extensions such as this one, it's important to also publish to OpenVSX.

Some extensions have been auto-imported by OpenVSX, but there seems to be a loading issue for some of them. Unfortunately it appears that there for a few extensions including this one (connorshea.vscode-ruby-test-adapter), and also swellaby/vscode-rust-test-adapter#194 that are affected by this issue. The symptoms are related to files missing within the packaged .vsix file distributed by OpenVSX, and log output can be seen in #56.

It should be relatively easy to publish either manually or via GitHub Actions workflow automation. You can claim ownership of the extension on OpenVSX if you haven't already and publish a working version.

Below is some more info from OpenVSX's extension publishing letter template:

OpenVSX Info / Request Template

Dear extension author, Please publish this extension to the Open VSX marketplace.

Context

Unfortunately, as Microsoft prohibits usages of the Microsoft marketplace by any other products or redistribution of .vsix files from it, in order to use VS Code extensions in non-Microsoft products, we kindly ask that you take ownership of the VS Code extension namespace in Open VSX and publish this extension on Open VSX.

What is Open VSX? Why does it exist?

Open VSX is a vendor neutral alternative to the MS marketplace used by most other derivatives of VS Code like VSCodium, Gitpod, OpenVSCode, Theia-based IDEs, and so on.

You can read on about Open VSX at the Eclipse Foundation's Open VSX FAQ.

How can you publish to Open VSX?

The docs to publish an extension can be found here. This process is straightforward and shouldn't take too long. Essentially, you need an authentication token and to execute the ovsx publish command to publish your extension. There's also a doc explaining the whole process with an example GitHub Action workflow.