Skip to content

Use HaaLeo/publish-vscode-extension for VS Code and Open VSX publishing#73

Open
Swahjak wants to merge 1 commit intomoetelo:masterfrom
toppynl:feat/publish-open-vsx-registry
Open

Use HaaLeo/publish-vscode-extension for VS Code and Open VSX publishing#73
Swahjak wants to merge 1 commit intomoetelo:masterfrom
toppynl:feat/publish-open-vsx-registry

Conversation

@Swahjak
Copy link

@Swahjak Swahjak commented Jan 6, 2026

Summary

  • Switch from direct vsce CLI to HaaLeo/publish-vscode-extension action
  • Add support for publishing to Open VSX registry
  • Add conditional publishing based on token availability

Closes #61

Migration Guide

New Secret Required

To enable publishing to Open VSX registry, add the following secret to your repository:

Secret Name Description
OPEN_VSX_TOKEN Personal Access Token from Open VSX

How to get an Open VSX token

  1. Go to https://open-vsx.org/
  2. Sign in with your GitHub account
  3. Go to Settings → Access Tokens
  4. Create a new token with publish permissions

Existing Secrets

The existing VS_MARKETPLACE_TOKEN secret is still used for VS Code Marketplace publishing (no changes required).

Conditional Publishing

Both publishing steps are conditional:

  • If OPEN_VSX_TOKEN is not set, Open VSX publishing is skipped
  • If VS_MARKETPLACE_TOKEN is not set, VS Code Marketplace publishing is skipped

This allows gradual adoption without breaking existing workflows.

- Add conditional publishing based on token availability
- Support both VS Code Marketplace and Open VSX registries
- Remove direct vsce dependency in favor of the action
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

publish Twiggy to OpenVSX / Ecslipse Foundation registry for extension install in VSCodium?

1 participant