Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

BUG: WinGet release uploads with the wrong hash

See original GitHub issue

Checks

I have checked that this issue has not already been reported.
I am using the latest version of Flow Launcher.

Problem Description

WinGet release uploads with the wrong hash, most likely due to dual release steps in the appveyor.yml on merge to master.

https://github.com/microsoft/winget-pkgs/pull/103060#discussion_r1173218090

To Reproduce

Screenshots

No response

Flow Launcher Version

Windows Build Number

Error Log


Replace this line with the important log contents.

Issue Analytics

State:
Created 5 months ago
Comments:12 (10 by maintainers)

Top GitHub Comments

1reaction

jjw24commented, Jun 7, 2023

the release is only published when manually promoted from draft, which should ensure the winget action fires only once.

Yes this would be the goal.

the tag build job does not affect the release process and therefore you don’t need to wait for it to finish.

I suppose setting it to APPVEYOR_REPO_TAG: false makes sense if the previous steps do not create a tag, but if a tag is created when a draft release is created, I do not think this entire step is necessary. I do not know if this is the case that the tag is created before this step, so please test when working on this issue.

0reactions

github-actions[bot]commented, Jul 31, 2023

This issue was closed because it has been stale for 7 days with no activity. If you feel this issue still needs attention please feel free to reopen.