Skip to content

Add Uninstaller Switches and Success Codes to Manifest Schema #5734

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.

Sign up for GitHub

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

Open
dkbennett wants to merge 7 commits into
base: master
Choose a base branch
from
Open

Add Uninstaller Switches and Success Codes to Manifest Schema #5734

Show file tree
Hide file tree
Changes from 6 commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
ec2e963
Schema update
dkbennett Sep 15, 2025
1226bf8
Merge branch 'master' into UninstallSchemaUpdate
dkbennett Sep 19, 2025
c2f626a
Implement Uninstaller Success Codes
dkbennett Sep 21, 2025
b3c68f7
Add Uninstallerswitches schema
dkbennett Sep 22, 2025
8c546d9
Remove success code usage until after manifest retrieval is in
dkbennett Sep 22, 2025
5c59566
Update release notes
dkbennett Sep 22, 2025
b69b322
Fix schema formatting
dkbennett Sep 25, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions doc/ReleaseNotes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,7 @@
* MCP server available; run `winget mcp` for assistance on configuring your client.
* App Installer now uses WinUI 3. The package dependency on WinUI 2 has been replaced by a dependency on the Windows App Runtime 1.7.
* Manifest schema and validation updated to v1.12. This version update adds "Font" as an InstallerType and NestedInstallerType.
* Added UninstallerSwitches and UninstallerSuccessCodes to the manifest schema for v1.12.

## Bug Fixes
* Manifest validation no longer fails using `UTF-8 BOM` encoding when the schema header is on the first line
Expand Down
Loading
Loading