-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Enhancements to upgrade (Apps that upgrade themselves) #1163
Comments
Isn't this the same as #1137 but targeting a superset of packages as the other issue is only concerned with forced upgrades on launch where this is for all packages that will upgrade themselves, but not necessarily force an upgrade? |
I think it's best to only have it not show updates for ones that force update on launch. If the app can be updated thought the program at any time it should still fit under the update --all parameter Update on launch of program. Should be blocked. Update with in program. Should still show up. |
We're thinking about these, and we have looked a bit into the future regarding our plans to support package pinning #476. This would align with pinned packages don't automatically get upgraded with How about: Installers:
- InstallerType: exe
InstallerArchitecture: x64
InstallerSHA256: 12341234123412341234123412341234123412341234
InstallerURL: https://www.contoso.com/awesomeapp/1.0.0/awesomeapp.x64.exe
RequireExplicitUpgrade: true |
winget-cli/schemas/JSON/manifests/v1.1.0/manifest.installer.1.1.0.json Lines 367 to 370 in 5a97e26
|
Description of the new feature/enhancement
Several packages manage upgrades themselves. One example is Visual Studio Code.
Proposed technical implementation details (optional)
Add a key to the manifest to identify packages with this capability.
When the user executes
winget upgrade
this package would either not be displayed (as having an upgrade available), or it would be displayed in a manner that indicates this behavior.When the user executes
winget upgrade --all
this package would not be upgraded.To be in line with
--include-unknown
we should add--include-automatic
.We may also want to consider
--force
to apply all--include-<*>
options.The text was updated successfully, but these errors were encountered: