Skip to content

docs: clarify OIDC vs PAT publishing in README - W-24756661 - #211

Open
madhur310 wants to merge 1 commit into
mainfrom
ms/W-24756661-readme-oidc-clarifications
Open

madhur310 wants to merge 1 commit into
mainfrom
ms/W-24756661-readme-oidc-clarifications

Conversation

@madhur310

Copy link
Copy Markdown
Contributor

Summary

  • Clarifies VSCE_PERSONAL_ACCESS_TOKEN is only required for PAT-based publishing (not needed with OIDC trusted publishing via the new vscode/publish-release-vsix composite action from feat(vscode): add OIDC-compatible publish-release-vsix composite action - W-24756661 #207).
  • Clarifies that the Trusted Publishing policy must be registered against the calling repo's own workflow filename (e.g. publishVSCode.yml), not the composite action's -- the prior wording ("this exact workflow filename") was ambiguous about which file it referred to.

Follow-up docs fix found while wiring OIDC into forcedotcom/salesforcedx-vscode's real publish pipeline.

🤖 Generated with Claude Code

VSCE_PERSONAL_ACCESS_TOKEN is only needed for PAT-based publishing, not
OIDC. The Trusted Publishing policy must be registered against the
calling repo's own workflow filename, not the composite action's -- the
prior wording was ambiguous about which file "this exact workflow
filename" referred to.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@madhur310
madhur310 requested a review from a team as a code owner November 12, 2026 22:37
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