Publish latest versions to OpenVSX registry

[danhuggins1992]

We utilise Gitpod and this plugin is a clear favourite for many developers, but we can only use OpenVSX registry plugins. The version in there is currently causing some issues and we believe the patch is in the newer versions. Can we request the new versions to be released to OpenVSX

[rogerlin0330]

The same here. I use WindSurf, which can only use OpenVSX registry plugins. Thus, the fix in 0.43.1 cannot be applied to WindSurf now, and WindSurf cannot recognize Junit Tests anymore due to the Jacoco version issue.

[rgrunber]

I was wondering the same thing a while ago, because in extensions like vscode-java, we do publish to both registries. However, it seems like vscode-java-test only publishes to the VS Code Marketplace. The Open VSX publishing aspect is done at https://github.com/EclipseFdn/publish-extensions/issues/851 , and it seems like they're running into some issues. Haven't seen any movement there in a bit.

[jdneo]

@rgrunber We do not publish to OpenVSX by ourselves. I think some one from (maybe OpenVSX?) is doing the publishes.

[github-actions[bot]]

Hi @danhuggins1992, I'm an AI Support assistant here to help with your issue. While the team reviews your request, I wanted to provide some possible tips and documentation that might help you in the meantime.

The OpenVSX registry is updated via manual publish steps. Here are a few references to get the latest Java extension versions published:

High-confidence references

• Trouble publishing to Open VSX (redhat-developer/vscode-java#1353 comment)

  • Claim the redhat namespace in OpenVSX (see How to claim a namespace) and publish using the suggested workflow
  • URL: https://github.com/redhat-developer/vscode-java/issues/1353#issuecomment-607775713

• Publish extension to Open VSX Registry (microsoft/vscode-gradle#679)

  • Add a CI/CD step to deploy every release to OpenVSX; procedure is documented in the OpenVSX wiki
  • URL: https://github.com/microsoft/vscode-gradle/issues/679

Other references with low confidence

• Support s390x for Red Hat Dev Spaces (redhat-developer/vscode-java#2837 comment)
  • Example of publishing a “universal” VSIX via ovsx publish -p ... --target universal as a fallback on OpenVSX
  • URL: https://github.com/redhat-developer/vscode-java/issues/2837#issuecomment-1382108600

The team will respond to your issue shortly. I hope these suggestions are helpful in the meantime. If this comment helped you, please give it a 👍. If the suggestion was not helpful or incorrect, please give it a 👎. Your feedback helps us improve!