Repository navigation
Breaking changes to properly justify a 2.0 release #2128
Description
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
Activity
Trenly commentedon Aug 3, 2022
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 -
denelon commentedon Mar 5, 2023
Additional asks in:
Trenly commentedon Jun 16, 2023
[Policy] Breaking-Change
sredna commentedon Jul 20, 2026
If
DefaultInstallLocationis ever going to be used by WinGet to find an existing install, its format should be restricted to sensible values.My recommendation is that the pattern should be restricted to
"pattern": "^[%\\]"which covers the following cases:%ProgramFiles%\MyAppand%LocalAppData%\Programs\MyApp(The recommended paths for 99% of apps)\AppInRootOfDrive(WinGet would check all local drives when a path starts with\)\Program Files\MyApp(Handles the case where an app hard-codesc:\Program Filesinstead of using the correct shell folder)\\Computer\Share\MyApp(This would not be allowed in the community repo. but might be useful in private sources. WinGet would treat something starting with\\as an absolute path)