The VS Code extension release builds and passes its tests, then fails at Marketplace publication because this repository has no VSCE_PAT publisher credential. The package release is successful; this is a separate workflow.
Observed in the 0.2.719 extension release. The same missing credential was recorded after the distinct extension-ID correction in #2020.
Acceptance:
- Add the existing authorized Stacks Marketplace publisher credential as the repository's
VSCE_PATActions secret through the normal owner-controlled secret setup. - Rerun the existing extension workflow without bypassing publication or weakening its checks.
- Verify the published
Stacks.vscode-stxversion and retain the successful workflow result.
Do not expose credential values in issues, logs or artifacts. Source changes, successful package releases and the DevTools ZIP do not establish a successful Marketplace publication.