[X] I have verified this is the correct repository for opening this issue.
[X] I have verified no other issues exist related to my problem.
[X] I have verified this is not an issue for a specific package.
[X] I have verified this issue is not security related.
What You Are Seeing?
There are places we have missed in the release of v2.0.0 that we aren't normalizing the version numbers when displaying or using these.
As Chocolatey CLI normalizes the version numbers, we should do the same in CHocolatey GUI.
What is Expected?
That every place that displays, or uses version numbers as a string forces the use of normalized version numbers even if the upstream package wasn't created this way.
How Did You Get This To Happen?
N/A
System Details
Operating System: Windows 10
Windows PowerShell version: Windows PowerShell 5.1
Checklist
What You Are Seeing?
There are places we have missed in the release of v2.0.0 that we aren't normalizing the version numbers when displaying or using these. As Chocolatey CLI normalizes the version numbers, we should do the same in CHocolatey GUI.
What is Expected?
That every place that displays, or uses version numbers as a string forces the use of normalized version numbers even if the upstream package wasn't created this way.
How Did You Get This To Happen?
N/A
System Details
Installed Packages
Output Log
Additional Context
This is issue is created in combination with CLI issue: https://github.com/chocolatey/choco/issues/3174