Skip to content
Build and Package

Fix VS Code extension Launch and Debug failing when AppxManifest.xml is at workspace root #1047

Sign in to view logs

Fix VS Code extension Launch and Debug failing when AppxManifest.xml is at workspace root

Fix VS Code extension Launch and Debug failing when AppxManifest.xml is at workspace root #1047

Triggered via pull request April 6, 2026 18:00
@chiaramooneychiaramooney
synchronize #385
copilot/fix-vscode-extension-launch-debug
Status Success
Total duration 18m 41s
Artifacts 5

build-package.yml

on: pull_request
build-and-package
12m 9s
build-and-package
validate-docs
2m 1s
validate-docs
mark-metrics-stale
6s
mark-metrics-stale
e2e-test
6m 15s
e2e-test
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
mark-metrics-stale
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v7. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build-and-package
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/github-script@v7. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
e2e-test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
cli-binaries
62.2 MB
sha256:8fbbfbece25fd974c96c0dc055d2d617f8e3e61f21bce3724827cc9925099bd1
msix-packages
24.8 MB
sha256:96e44a3415dd78c4bfe5cbfa3dfc70e652a45674e29f9ef18f81ab2f3055c66a
npm-package
25 MB
sha256:e4f9b36d248d6fbcf56bd8e337fb68953ac071b87a5052fe44823251d1022680
nuget-packages
25.1 MB
sha256:86c2d40ed8e1a02200a5ae99571254e54b8952f2f04164d1cbf1e8b75d622ab3
test-results
439 KB
sha256:16a23400efedc35590103cc295b640a90901ffc459c5cde99bdb6cf93581e885