docs: add VS Code extension OIDC publishing guide#119
Draft
theoephraim wants to merge 1 commit into
Draft
Conversation
Step-by-step guide for publishing a VS Code extension via Azure workload identity federation (OIDC) instead of an expiring VSCE_PAT, with copy-paste az/gh scripts — including the non-obvious Marketplace publisher permission step (Team Foundation Identity ID) and common gotchas. Linked from the README docs index and the configuration.md vscode example.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a guide for publishing a VS Code extension from CI via Microsoft Entra workload identity federation (OIDC) instead of an expiring
VSCE_PAT, using bumpy's custompublishCommand.The setup is genuinely awkward (especially the Marketplace publisher permission step), so the guide is heavy on copy-paste
az/ghscripts:azure/login(OIDC) →bumpy ci release→vsce publish --azure-credential(bumpy's child process inherits theazsession).publishCommandwith--azure-credential, and theazure/loginworkflow step (with gating onbumpy ci plan).won't-accept-id,AADSTS5000225inactivity, personal-MSA publisher, unhelpful publish errors.Linked from the README docs index and the
configuration.mdVSCode example.