Open carlocab opened 3 years ago
We had a release of v1.3.3 which was in draft initially, it was then removed and after few days a proper v1.3.3 release was made. Did the SHA get cached somewhere when it was a draft release? I am not really sure what is happening.
Homebrew hasura-cli
was upgraded to v1.3.3 here: https://github.com/Homebrew/homebrew-core/pull/64534
It seems you have this process automated somehow. I suspect that this was still a draft release when this happened.
@chenrui333 FYI, I think your bump action picked up a draft release.
We didn't bump action as part of our release. The homebrew package is community maintained, so quite surprised somebody picked this up in draft stage.
Is it possible to send a new patch to override this https://github.com/Homebrew/homebrew-core/pull/64534?
Someone's already opened a PR to fix the recorded SHA256: https://github.com/Homebrew/homebrew-core/pull/67065
As for the bump action, I'm not sure how that got set up, so I don't know how to fix it.
We're attempting to update Homebrew's version of Go (https://github.com/Homebrew/homebrew-core/pull/66355).
While testing the new version, CI produced the following error:
I can update the sha256 associated with the formula, but CI will come back to me with the following error:
Can I confirm that nothing is amiss here?