Kaleb Luedtke
Kaleb Luedtke
@nvt223 - - Are you still experiencing this issue with the [latest release](https://github.com/microsoft/winget-cli/releases/latest) of the cli?
It seems the inconsistencies are related to the console width and the ID's being truncated. In some fonts the character appears as `...`, but depending on system settings the character...
Does it work if you just run `winget upgrade --id XP8DCGQ3K6VLD` ?
I know its not a perfect solution, but the log level can be controlled through the settings file - which could be written in the runner before executing winget https://learn.microsoft.com/en-us/windows/package-manager/winget/settings#logging-settings...
[Policy] Area-Settings
[Policy] Command-Upgrade
@denelon - I recall a separate issue specific to the V2 index dropping trailing zero's if the version only had two parts, let me find that, as it's the root...
That could be true, but I've seen quite a few PRs recently that were using WingetReleaser V2 (according to the PR description) that were still on Manifest Version 1.5.0 For...
For additional context - `portable` installers (loose binaries) do not need to write anything to the Registry. The version that is currently used for WinGet appears to be an `inno`...
I would say that the `update` command doesn't seem like a logical home for this functionality to me - although I understand it is because there isn't all the option...