Winget-cli: Apps installed should optionally auto-update

[TravisSpomer]

Description of the new feature/enhancement

If I install something with winget, it should update automatically in the background without me ever having to explicitly tell it to, like most existing package managers and launchers on Windows: the Windows Store, Steam, Adobe Creative Cloud, and so on.

Proposed technical implementation details

• Some people won't want this, so it should be possible to disable the behavior via a setting.
• It's plausible that someone might want to update everything automatically except for a single package, perhaps one that introduced a severe breaking change. The package registry could split it into badapp and badapp-legacyfork but it would be far preferable to be able to say "update everything automatically except badapp". (Conversely, some users who might want to turn off auto-updates entirely might still want one or two packages to indeed update automatically.)
  
  
  
  • In addition to that user setting, some individual packages might want to block automatic updates regardless of user preferences.
  
  
• winget should probably only automatically update apps to versions that have been released (and not recalled) for a week or some other holding period, to avoid a situation where a bad update immediately breaks thousands of people across the world.
• When running the update command manually, in addition to updating packages normally, winget should tell me of the changes it made automatically since the last update.

[RichiCoder1]

I'm not sure about auto-updating, but update-all with support pin-ing packages and the ability for maintainers to mark their packages as having their own auto-updates would be great.

[TravisSpomer]

From my perspective, initially getting and installing tools is something I do once a year or so, but updating is something I need to do constantly, so that's where there's the most room for improvement from something like winget. Requiring me to manually start up a terminal and run a command every week or so seems very last-century, when it's something that could have easily been done for me when I wasn't around. Without automatic updates, using a package manager just doesn't seem useful enough to bother.

Initially I was thinking that it would be a good compromise to just notify me in some fashion when an update is available, but I imagine most people would end up using one tool that updated constantly, which would just turn the notifications into annoying noise.

[NicTanghe]

From my perspective, initially getting and installing tools is something I do once a year or so, but updating is something I need to do constantly, so that's where there's the most room for improvement from something like winget. Requiring me to manually start up a terminal and run a command every week or so seems _very_ last-century, when it's something that could have easily been done for me when I wasn't around. Without automatic updates, using a package manager just doesn't seem useful enough to bother.

I c what you mean but if auto updating is the way that is chosen packages auto update should be togglable.
And conflicts with dependancies should always be mentioned and then not update packages that depend on the same thing that cant auto update becouse it is a dependancy for another package.

Also managing range of version dependencies aka compatible with version 1.0 - 1.79 seems like mess to maintain / enforing people to update their package when their dependancy has an update seems like a monumental task.