Skip to content

Update Microsoft.WindowsAppSDK to 1.8 stable (#837) #1772

Update Microsoft.WindowsAppSDK to 1.8 stable (#837)

Update Microsoft.WindowsAppSDK to 1.8 stable (#837) #1772

Re-run triggered April 2, 2026 19:01
Status Success
Total duration 1h 3m 19s
Artifacts 43

build.yml

on: push
Matrix: build
Matrix: package
Matrix: sign
Matrix: release
Fit to window
Zoom out
Zoom in

Deployment protection rules

Reviewers, timers, and other rules protecting deployments in this run
Event Environments Comment
michael-hawker
approved Apr 2, 2026
nuget-release-gate and nuget-release-gate

Release 8.3-260402-preview2 to NuGet with 1.8 WASDK support

Annotations

8 warnings
build (3, wasdk)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-dotnet@v4, actions/upload-artifact@v4, al-cheb/[email protected], darenm/setup-vstest@3a16d909a1f3bbc65b52f8270d475d905e7d3e44, microsoft/setup-msbuild@v2. 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 (3, wasdk)
No files were found with the provided path: D:\a\Windows\Windows/**/*.dmp. No artifacts will be uploaded.
package (3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-dotnet@v4, actions/upload-artifact@v4, microsoft/setup-msbuild@v2. 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/
package (2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-dotnet@v4, actions/upload-artifact@v4, microsoft/setup-msbuild@v2. 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/
sign (3)
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/setup-dotnet@v4, actions/upload-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/
sign (2)
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/setup-dotnet@v4, actions/upload-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/
release (3)
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/setup-dotnet@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/
release (2)
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/setup-dotnet@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
build-logs-wasdk-winui3
12.6 MB
sha256:29860fc4279d277acc237b82250e9704ecf2baf8ad5ce1693b9a97d6e1f66a92
build-logs-winui2
61 MB
sha256:ade4eb42a20d090766d48ce7612c41a7273b454eed010c03353575cf13243fb4
build-logs-winui3
50.4 MB
sha256:f4d72234bac52de5bfab5b35afee62143a4426e5dc2eb7bebf0383fca5998f43
ilc-repro-wasdk-winui3
1.17 MB
sha256:fa18eda6ac624a4f0f49bdf7d0d179f13ea5c8bf78219b70e3c65188ebfa858a
nuget-list-2
181 Bytes
sha256:8ee188804f4da02a27c8cb4fc8a70f08e018ee51c160e3a6e3c6f9724f13299f
nuget-list-3
181 Bytes
sha256:8ee188804f4da02a27c8cb4fc8a70f08e018ee51c160e3a6e3c6f9724f13299f
nuget-packages-winui2
12 MB
sha256:d7feb43562a0d45e88dc9e73f8a975c3030c6220273711c8e3a7220326d2bf42
nuget-packages-winui3
10.5 MB
sha256:d4e754f67b9407199d4886de6041d7f556247d2f5de2aa4a155ed9cac1b1ebd7
signed-nuget-packages-2
13.7 MB
sha256:279c97959a9de36d8ab08ce4e75f500406824132ae3898c8bde2d3161fdb550e
signed-nuget-packages-3
12 MB
sha256:b9a16134536890651eeffec61c77293a4c6277f1f59398f85cc13c7ad26cec86
vstest-diagnostic-log-wasdk-winui3.txt
96.8 KB
sha256:dbe65e38ed1219f4deef43f7155a88b7045b39f8c7154c81a2afa9357d29033c