Closed mergify[bot] closed 1 day ago
🤖 Your WebAssembly Sample App stage site is ready! Visit it here: https://unowasmprstaging.z20.web.core.windows.net/pr-18864/index.html
🤖 Your Docs stage site is ready! Visit it here: https://unodocsprstaging.z13.web.core.windows.net/pr-18864/index.html
The build 147891 found UI Test snapshots differences: android-28-net8
: 23, android-28-net8-Snap
: 41, ios
: 13, ios-Snap
: 61, skia-gtk-screenshots
: 57, skia-linux-screenshots
: 59, skia-windows-screenshots
: 66, wasm
: 396, wasm-automated-net9.0-UWP-Default-automated
: 24, wasm-automated-net9.0-UWP-RuntimeTests-0
: 0, wasm-automated-net9.0-UWP-RuntimeTests-1
: 0, wasm-automated-net9.0-UWP-RuntimeTests-2
: 0, wasm-automated-net9.0-WinUI-Benchmarks-automated
: 0, wasm-automated-net9.0-WinUI-RuntimeTests-0
: 0, wasm-automated-net9.0-WinUI-RuntimeTests-1
: 0, wasm-automated-net9.0-WinUI-RuntimeTests-2
: 0
GitHub Issue (If applicable): closes https://github.com/unoplatform/uno/issues/18796
PR Type
What kind of change does this PR introduce?
What is the new behavior?
Ensures that nuget targets can still be called when a RID is not matching wasm.
PR Checklist
Please check if your PR fulfills the following requirements:
Screenshots Compare Test Run
results.Other information
Internal Issue (If applicable):
This is an automatic backport of pull request #18853 done by Mergify.