OpenVSX/Marketplace publishing for cdt.cloud

Summary

Eclipse-CDT-Cloud maintains multiple VS Code Extensions:

• https://github.com/eclipse-cdt-cloud/vscode-memory-inspector
• https://github.com/eclipse-cdt-cloud/vscode-websocket-adapter
• https://github.com/eclipse-cdt-cloud/cdt-gdb-adapter
• https://github.com/eclipse-cdt-cloud/vscode-trace-extension
• https://github.com/eclipse-cdt-cloud/vscode-peripheral-inspector
• https://github.com/eclipse-cdt-cloud/vscode-trace-extension
• https://github.com/eclipse-cdt-cloud/vscode-trace-server

Currently these extensions are published to OpenVSX/VSCode marketplace in the eclipse-cdt namespace. The CDT-Cloud team now would like to migrate to a dedicated namespace called eclipse-cdt-cloud. This would enable a clean separation and makes it easier for users to identify from which project a component is coming from.

Therefore, could you please set up the eclipse-cdt-cloud namespace/organization an create and API token for each marketplace? Instructions can be found here:

• https://github.com/eclipse/openvsx/wiki/Publishing-Extensions#3-create-an-access-token
• https://code.visualstudio.com/api/working-with-extensions/publishing-extension#get-a-personal-access-token

Once these tokes are available, we would like to use them in our Github Action workflows. So please add these secrets to the https://github.com/eclipse-cdt-cloud organisation.

Priority

• Urgent
• High
• Medium
• Low

Severity

• Blocker
• Major
• Normal
• Low

Impact

(What is the impact of this issue? Is it blocking a release? Are there any time constraints?, for example: "We have a release tomorrow")