WinGet 1.7 manifest schema

[denelon]

Description of the new feature / enhancement

This is a parent issue to track outstanding schema requests for the 1.7 schema. Inclusion in this list is not a commitment. Other schema items may be added or removed.

• Manifest fields for custom uninstall arguments and return codes #1885
• Add DSC Resource identifier to WinGet manifests #3523
• Support licenses for Microsoft Store Apps (offline installation) #3354

Proposed technical implementation details

No response

[R-Adrian]

can we please also get package exclusion without pinning a specific version? #2339

examples of currenlty broken / misidentified packages that need to be ignored (or listed in the packages manifest only for supporting initial installation but not for updates via winget?)

Discord.Discord - this one updates itself in the background but when it updates itself it leaves behind the version number from the initial installer in the registry and this confuses winget but not the Discord app itself - that one uses a different version detection mechanism and runs normally.

Mozilla.Firefox.DeveloperEdition - this one shows a "stable" version number in the registry and this confuses winget. The app itself does not use the registry for the version detection mechanism and it does normal self-updates in the background.

edit: i see that package exclusion is coming with winget version 1.6 in a few days... hooray. Milestone v1.6 Client: https://github.com/microsoft/winget-cli/milestone/40
in my opinion though, winget still needs support for only initial installation of such packages, without attempting to update them (because it will most likely break their current configuration) #3482
/edit