Closed m2u-84 closed 1 year ago
Thanks for reporting the bug! It appears that the packaged file was uploaded before making a git tag, which is our system for including the version file.
This is not a bug, but rather an accident made while publishing Cmder. We'll fix it by replacing the ZIP files with updated ones containing the right version info file.
Good catch!
Update: I believe we'll avoid editing the ZIP file and make a new release instead. For anyone interested, please read the follow-ups at: https://github.com/cmderdev/cmder/issues/2818#issuecomment-1648709904
We should cut a new release so chocolatey can ingest the change. Otherwise you have to ask them to manually create a new package. Ask me how I know. 🤔
Hopefully if the package maintainers give us access, I can automate some parts so whenever a new version is released, it'll auto update on package managers
The current GitHub workflow doesn't build on tags, which may explain the mismatch.
Simply replacing the zip files on a release cause the chocolatey issue. It is more of an issue with a functional bug fix less important here.
They trigger on a release creation.
This is marked closed, but the issue still exists. Or at least, the files in the download link claim to be 1.3.20 (not .21).
@chrisant996 You're right, answered in the duplicate issue here:
https://github.com/cmderdev/cmder/issues/2818#issuecomment-1648709904
Version Information
Cmder Edition
Cmder Mini
Description of the issue
I just updated to the latest version (1.3.21) of the cmder Mini release and noticed, that the version info has not been raised. The version file in the ZIP root as well as the EXE meta info are still showing 1.3.20 for me (1.3.20.151 to be exact). I also checked the full version but it has the same issue. This is what I see with the latest files:
How to reproduce
Additional context
No response
Checklist