Limit marketplace publishing tokens to the publish steps - #1297
Merged
Merged
Conversation
vscode-release.yml only publishes to the VS Code Marketplace and Open VSX; npm publishing lives in release.yml and already runs over OIDC. Nothing in this workflow reads NPM_TOKEN, so drop it. Assisted-By: devx/d9810122-2b8f-4f8d-b51b-eb980219e4b6
VSCE_PAT and OVSX_PAT were set at the workflow level, so every step, including pnpm install and the build, could read them. Only the vsce and ovsx publish steps need them, so move the tokens onto those steps. vsce show uses the public gallery API and does not need the PAT. Assisted-By: devx/d9810122-2b8f-4f8d-b51b-eb980219e4b6
graygilmore
force-pushed
the
gg-scope-release-secrets
branch
from
September 11, 2026 23:12
ab176cb to
c05c2be
Compare
Assisted-By: devx/1fcb32d2-4780-44a8-8dc3-0c25314bc391
EvilGenius13
approved these changes
Sep 16, 2026
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
3 participants
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.
The release workflows exposed release credentials more broadly than needed.
VSCE_PAT,OVSX_PAT, and repo credentials were available to install/build steps even though only specific release steps need them.This PR tightens that up:
NPM_TOKENfromvscode-release.yml. That workflow only publishes to the VS Code Marketplace and Open VSX; npm publishing lives inrelease.ymland already runs over OIDC.VSCE_PATandOVSX_PATfrom workflow-levelenv:onto thevsce publishandovsx publishsteps in both workflows.vsce showhits the public gallery API and doesn't need the PAT.GITHUB_TOKENfrom both workflows.GITHUB_TOKENscoped tochangesets/actioninrelease.yml, then clears the.netrccredentials that action writes before the marketplace publish steps.contents: readpermissions to the manual VS Code release workflow.Marketplace publishing authentication is unchanged; the required tokens are still available to the publish commands that need them.
Tophatting
There should be no functional changes. The next
release.ymlrun onmainthat ships a VS Code extension version bump should still publish to both marketplaces. If either publish step fails with an auth error, the env didn't make it onto the step.