-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Latest release changed Microsoft.UI.Xaml dependency, breaking some items #4208
Comments
This comment was marked as off-topic.
This comment was marked as off-topic.
@stephengillie - this is not "Area-External" |
Release Microsoft.UI.Xaml v2.8.6 · microsoft/microsoft-ui-xaml (github.com) doesn't have the .msix installer for WinGet to consume. We're working with them to see if we can get the .msix package published. This wasn't detected as the framework package from the Microsoft Store automatically handles the dependency for the Microsoft Store upgrade flow. We will be adding tests for future releases. |
Update: The .appx packages have been added to the release for UI.XAML |
App Installer PR in validation: |
Closing this as the Appx package for the dependency is now available on GitHub and the PowerShell module has been updated so that |
Brief description of your issue
With the release of Windows Package Manager 1.7.10582, the dependency on Microsoft.UI.Xaml has been bumped from v2.7.3 to v2.8.6. The microsoft/microsoft-ui-xaml release doesn't have appx installers so the Sandbox Test script at winget-pkgs is broken.
Repair-WinGetPackageManager
still points to Microsoft.UI.Xaml 2.7.3, and is therefore, broken. Additionally, all the documentation still refers to Microsoft.UI.Xaml 2.7Steps to reproduce
Install the PowerShell cmdlets and run
Repair-WinGetPackageManager
Expected behavior
WinGet to be installed successfully
Actual behavior
Environment
The text was updated successfully, but these errors were encountered: