Breaking changes to properly justify a 2.0 release

[denelon]

Description of the new feature / enhancement

In the spirit of semantic versioning, we want to identify issues that are potentially breaking changes to consider for a future 2.0 release. This list is not a commitment for what would be in a 2.0 release, but rather to identify candidates. This list may be amended over time, and any issues not taken into a 2.0 release should be moved to a similar Issue to identify a future 3.0 release.

• Cannot override installer hash as admin. Even if EnableLua = 0 (UAC OFF) #715
• Windows Package Manager 2.0 #2106
• Normalize --force to be for overriding default, conservative behaviors #2112
• Different UX modes for WinGet #2972

Proposed technical implementation details

No response

[Trenly]

I was looking through the list of issues and found this one which could be a consideration for a 2.0 release or to be dropped -

• Is there really a significant benefit in allowing InstallerType on the package-level? #429

[denelon]

Additional asks in:

• Two suggestions for a 2.0 release #3047

[Trenly]

[Policy] Breaking-Change