Skip to content

Automate VS Code Marketplace publishing - #432

Draft
JoviDeCroock wants to merge 2 commits into
mainfrom
ci/publish-vscode-extension
Draft

Automate VS Code Marketplace publishing#432
JoviDeCroock wants to merge 2 commits into
mainfrom
ci/publish-vscode-extension

Conversation

@JoviDeCroock

Copy link
Copy Markdown
Member

Summary

  • version the private VS Code extension through the existing Changesets release PR
  • detect unpublished Marketplace versions and publish the exact packaged VSIX from the npm staging flow
  • authenticate with Microsoft Entra workload identity federation instead of a long-lived PAT
  • package and integrity-check the extension in CI, including its changelog

Release setup required

Before this can leave draft, configure VSCE_AZURE_CLIENT_ID and VSCE_AZURE_TENANT_ID on the protected npm environment, add the matching GitHub OIDC federation to the Entra application, and grant its service principal access to Marketplace publisher 0no-co.

The npm stage and Marketplace publish cannot be atomic. The release runbook documents recovery when Marketplace publishing fails after npm staging.

@changeset-bot

changeset-bot Bot commented Aug 24, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 88c6565

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
vscode-graphqlsp Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

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.

1 participant