Closed VishnuJin closed 6 months ago
The version numbers in Chocolatey CLI are normalized when returning them. In Semver v2, leading zeroes are removed from version number 'parts', so 4.6.00081.20150925
becomes 4.6.81.20150925
.
In previous versions of Chocolatey CLI (pre 2.x), the version number provided would be the version number used (so if you had zeroes in your version number, it would be used on the Chocolatey Community Repository).
In 2.x versions of Chocolatey, if you provide a version number with leading zeroes in your package, it will be normalized to remove them. So when it is submitted to the Chocolatey Community Repository, those zeroes will not be there.
Because of the age of that package (it was submitted on 26 September 2015), it was submitted with a pre 2.x version of Chocolatey CLI, it uses the package version with leading zeroes.
We do some work behind the scenes to ensure that we can match those versions when you are managing or searching for packages.
I'm going to go ahead and close this as there is nothing for us to do here.
Checklist
What You Are Seeing?
For example - https://community.chocolatey.org/packages/DotNet4.6-TargetPack#versionhistory latest version of DotNet4.6-TargetPack is shown as
4.6.00081.20150925
in WebUi but choco list just showsWhat is Expected?
also output
DotNet4.6-TargetPack 4.6.00081.20150925
How Did You Get This To Happen?
choco find -e DotNet4.6-TargetPack
System Details
Installed Packages
Output Log
Additional Context
No response