-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
Update WinGet configuration file location & extension #37673
base: main
Are you sure you want to change the base?
Conversation
Related to: |
nice! |
can we move the .configurations into the .config folder? |
My only concern would be if others start to adopt the powertoys way since it has been mentioned as a "reference repository" in quite a few places |
I agree @mdanish-kh. The guidance is written as: ".config/configuration.winget" <- Default Configuration It could be confusing to have the following since we no longer reference a ".configuration" directory. "./config/.configurations/configuration.winget" |
I misread the paths, sorry, you did it correct |
@mdanish-kh I'm not sure it should close the issue. I think there might still need to be changes in the configuration files to handle the securityContext: elevated. The configurations work when run elevated, but in user scope, I think enabling developer mode fails (but checking if it's in the right state works) due to lacking administrator privileges. I don't remember if installing Visual Studio requires elevation or not. |
@denelon - I don't remember adding that bit in the description (looks like I'm right that I didn't 😆😆😄). Anyways, that makes sense & removed the closes issue ref |
Summary of the Pull Request
The new convention for WinGet configuration files if to place them in a
.config
directory with file extension.winget
. See https://learn.microsoft.com/en-us/windows/package-manager/configuration/create#file-naming-conventionPR Checklist
Detailed Description of the Pull Request / Additional comments
Validation Steps Performed