-
-
Notifications
You must be signed in to change notification settings - Fork 131
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update the binary on Winget #82
Comments
Yeah, I've also noticed that the pull request here microsoft/winget-pkgs#7037 has already been merged since February, but it's still not showing with the winget-cli. |
to be honest.. me neither, i just copied what the pr before me did |
In addition to the previous update PR, I saw this one microsoft/winget-pkgs#21601
Maybe an issue on their side that needs to be reported/resolved. It looks like their CI didn't like so maybe it's related. |
Digging this issue up a bit because, if i remember correctly, v3.0.1 was showing up at one point in the winget tool. Also, I'd like to risk a barely educated guess: can this issue be caused by the "v" prefix? It's only on the 3.0.1 release, and not on the 2.3.0 one. Moreover, I believe it would make sense for an upgrade tool to put letters before numbers in its ordering system, because of some release going "alpha x" or "beta y" before 1.0. Edit: somebody encountering the same problem with v-prefixes and it's been classified as a bug, so it's on winget's side. |
You're right. I have created a PR to fix this: As for auto-updating the Winget manifest, I have also created a PR to setup the Winget Releaser workflow: |
That's because the |
There seems to still be some wonky stuff with winget. It didn't upgrade OpenHashTab from 3.0.2 to 3.0.4 automatically with |
Hi dev,
Could you update the OpenHashTab file on the winget repo? Currently, it is showing 2.3.0 version there.
Thanks,
The text was updated successfully, but these errors were encountered: