Skip to content

Fix native dependency installation in signing jobs - #1142

Open
Bill Schnurr (bschnurr) wants to merge 1 commit into
microsoft:mainfrom
bschnurr:fix/signing-native-install
Open

Bill Schnurr (bschnurr) wants to merge 1 commit into
microsoft:mainfrom
bschnurr:fix/signing-native-install

Conversation

@bschnurr

Copy link
Copy Markdown
Member

Summary

  • Fix the signing job failure in DevDiv build 15947122.
  • Install signing tooling with npm ci --ignore-scripts to avoid rebuilding @vscode/windows-process-tree: the bundled node-gyp cannot recognize the agent's Visual Studio 18 installation.
  • Run npm rebuild @vscode/vsce-sign explicitly so manifest generation and signature verification retain their required executable. Extension build jobs and signature enforcement are unchanged.

Validation

  • Clean dependency installation through Microsoft's package proxy, followed by the targeted signing-binary rebuild.
  • Actual VSIX manifest generation using the freshly installed tooling.
  • npm run lint.
  • Targeted Prettier check and executable YAML parsing/assertions for the two npm steps.
  • Whitespace check (accounting for the repository's existing CRLF line endings).

The Azure signing pipeline has not been rerun locally; end-to-end signing still requires Azure CI.

Skip dependency lifecycle scripts when installing tooling for prebuilt VSIX signing, then initialize only the vsce signing binary. This avoids rebuilding windows-process-tree with an unsupported Visual Studio toolchain.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 35aea860-84b7-4f12-88da-cff7120df961
@bschnurr Bill Schnurr (bschnurr) added the bug Issue identified by VS Code Team member as probable bug label Nov 6, 2026
@bschnurr
Bill Schnurr (bschnurr) enabled auto-merge (squash) November 6, 2026 23:10
@bschnurr

Copy link
Copy Markdown
Member Author

Follow-up investigation found this PR targets an unused local signing template. The pre-release pipeline imports azure-pipelines/extension/templates/jobs/publish-extension.yml from DevDiv/Pylance-Eng, which invokes ../steps/sign.yml in that shared repository. This change therefore does not fix build 15947122. Auto-merge has been disabled; do not merge this PR as the build fix. The native-install correction belongs in the active shared Pylance-Eng signing template.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Issue identified by VS Code Team member as probable bug

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant