-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
New version: chrisant996.Clink version 1.4.20.236aba #97870
New version: chrisant996.Clink version 1.4.20.236aba #97870
Conversation
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
wingetbot, The check-in policies require a moderator to approve PRs from the community. Our moderators are community volunteers, please be patient and allow them sufficient time to review your submission. Template: msftbot/requiresApproval/moderator |
Publish pipeline succeeded for this Pull Request. Once you refresh your index, this change should be present. |
Hey @vedantmgoyal2009 if clink is auto-updated by itself, it does not write the final Git hash to the registry in the above listed Version field. As such, future WinGet upgrade calls result in WinGet thinking there is a newer version when there is not. Here is a sample output of me checking WinGet after Clink updates itself.
Is it possible for all future updates to only have the first 3 version number parts? I had originally filed this as a bug with chrisant996 directly, but he said this isn't something that is a problem on his side and he had no idea that Clink had a package in WinGet. I don't think he minds, but since it isn't working quite right I think this is the right place to fix it. Thanks. |
Result: Installation Failed
Auto-updated by vedantmgoyal2009/winget-pkgs-automation in workflow run 6283
Microsoft Reviewers: Open in CodeFlow