Publish to OpenVSIX Registry

[JustinGrote]

[Requested by @jpsnover]

We should publish to OpenVSIX registry as well for vscode forks and other tools to be able to utilize PowerShell.

vscode-powershell/docs/azure_data_studio/README_FOR_MARKETPLACE.md

Lines 58 to 67 in 01e8ef8

	## Installing the Extension
	You can install the official release of the PowerShell extension by following the steps
	in the [Azure Data Studio documentation](https://docs.microsoft.com/en-us/sql/azure-data-studio/extensions).
	In the Extensions pane, search for "PowerShell" extension and install it there. You will
	get notified automatically about any future extension updates!
	You can also install a VSIX package from our [releases page](https://github.com/PowerShell/vscode-powershell/releases) by following the
	[Install from a VSIX](https://code.visualstudio.com/docs/editor/extension-gallery#_install-from-a-vsix)
	instructions. The easiest way is through the command line:

Tasks

• Verify legal feasibility

• Verify CI pipeline feasibility

• Update README to clarify best-effort support for vscode forks and other OpenVSIX Consumers

• Publish Package

@andyleejordan can you verify the MS legal feasibility of this? You'd probably have to own the devops pipeline work as well.

[github-actions]

🎯 Agentic Issue Triage

Summary: This is a feature request to publish the vscode-powershell extension to the [Open VSX Registry]((openvsx.org/redacted) (the open marketplace used by VS Code forks such as VSCodium, Eclipse Theia, Gitpod, and others). The request was raised by @jpsnover. It requires MS legal sign-off, CI/CD pipeline work, and a small documentation update.

📋 Issue Breakdown

The issue already includes a clear task list:

• Verify legal feasibility — Microsoft legal review required before publishing to a third-party registry. @andyleejordan is called out to drive this.
• Verify CI pipeline feasibility — The existing Azure DevOps / GitHub Actions release pipeline needs to be extended to publish to Open VSX in addition to the VS Code Marketplace. This likely involves adding an ovsx publish step.
• Update README — Clarify that Open VSX / vscode-fork support is best-effort (not first-class).
• Publish package — Execute the publish once the above gates are cleared.

🔍 Context & Similar Art

• The linked file docs/azure_data_studio/README_FOR_MARKETPLACE.md already documents that the extension is not published to Open VSX, which this issue aims to change.
• Many popular Microsoft-affiliated extensions (e.g., Python, Jupyter) are now published to Open VSX; precedent exists within Microsoft for doing this.
• No duplicate open issues found.

🛠️ Implementation Notes

Publishing mechanics:

• The standard tool is ovsx (npm package ovsx).
• Open VSX requires a personal access token from [open-vsx.org]((openvsx.org/redacted) The token would need to be stored as a secret in GitHub/Azure DevOps.
• A typical CI step looks like:

  npx ovsx publish (vsix-file) -p $OVSX_PAT

• This can be added to the existing release workflow alongside the vsce publish step.

PAT ownership: Someone with an open-vsx.org account (ideally the ms-vscode or PowerShell namespace) needs to register and generate the token. This may itself require legal/policy review.

Namespace claim: The ms-vscode or PowerShell namespace on open-vsx.org may need to be claimed before publishing. Check (openvsx.org/redacted)

📚 Useful Resources

• Open VSX Publishing Guide
• [ovsx CLI npm package]((www.npmjs.com/redacted)
• [open-vsx.org]((openvsx.org/redacted)
• How other Microsoft extensions handle Open VSX (Python extension CI for reference)
• VS Code Marketplace vs Open VSX FAQ

Generated by Agentic Triage for issue #5470

To install this workflow, run gh aw add githubnext/agentics/workflows/issue-triage.md@2f03fdaafb8c1ae62dfde7e0be762a822a201aeb. View source at https://github.com/githubnext/agentics/tree/2f03fdaafb8c1ae62dfde7e0be762a822a201aeb/workflows/issue-triage.md.

[andyleejordan]

I believe anything published outside of the official VS Code marketplace will have to be done by the community...sorry!

[JustinGrote]

No worries, upon closer inspection it appears to me at a glance that everything that goes into the VSIX is MIT or Apache licensed, so I should be able to own this separately. I'll track any progress here.

[andyleejordan]

That you should! I think it's mostly a problem of the signature; I'm required to upload from a trusted environment to a trusted hosting platform, and they have not vetted OpenVSIX etc.