Closed smcclosr closed 3 months ago
Same issue with AntibodySoftware.WizTree
version 4.20
, UniGet truncated the tailing 0 and interpreted the package version as 4.2
Same issue with
AntibodySoftware.WizTree
version4.20
, UniGet truncated the tailing 0 and interpreted the package version as4.2
I think WizTree does not fall under this issue, because if you winget search wiztree
at the command prompt, it will come back with 4.2, not 4.20, so that is an upstream issue where WinGet as the wrong.
I am afraid this is a bug with WinGet. CPU-z is being reported as 2.1 by WinGet
there is an inconsistency here:
Are you running the prerelease winget version?
Not that I know of
what is the output of winget --version
and C:\Program Files\UniGetUI\winget-cli_x64\winget.exe --version
?
Both are the same, v1.8.1911
Huh, that is weird.
@denelon, sorry to ping you. Any ideas on what could be causing this behaviour? Could this issue be related to some kind of controlled feature rollout or A/B testing on WinGet?
there is an inconsistency here:
Please confirm these before moving forward
UniGetUI Version
3.1.1
Windows version, edition, and architecture
Windows 11 Pro 22621.3880 x64
Describe your issue
It looks like the tool truncates version number when the last digit is zero.
Steps to reproduce the issue
Go to Discover Packages, the search for cpuid.cpu-z there will be a list of packages, but the version will be 2.1, but if checked on the command line 'winget list cpuid.cpu-z' it will display version 2.10
UniGetUI Log
Package Managers Logs
Relevant information
No response
Screenshots and videos
No response