-
Notifications
You must be signed in to change notification settings - Fork 145
winget-releaser
failure during Update Windows packages
step: RequestError [HttpError]: other side closed
#2689
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
Comments
winget-releaser
failures during Update Windows packages
stepwinget-releaser
failure during Update Windows packages
step: RequestError [HttpError]: other side closed
Created a corresponding bug ticket on |
Interestingly, this did not occur with
If no no problems return with |
The issue did not return in |
The problem came back in 1.3.0:
Seems likely this is intermittent and we should expect it popping up randomly on releases. |
Version(s)
happens since the 1.1.1 release
Describe the bug
We are getting
RequestError
[HttpError
] when releasing Scala CLI onwinget
with thewinget-releaser
action.The error seems to be a false positive, as the relevant
winget-pckgs
PR is being created correctly and the update seems to work, otherwise.Fortunately, it is the last step, so no important actions are aborted because of this failure.
To Reproduce
Seems to happen on every Scala CLI release now. Just check the
Update Windows packages
step at the end of the release.Expected behaviour
When releasing Scala CLI, we shouldn't have false-positive errors.
Extra context
v1.1.2
release job: https://github.com/VirtusLab/scala-cli/actions/runs/7553378895/job/20567398955#step:6:106winget-pckgs
PR: New version: VirtusLab.ScalaCLI version 1.1.2 microsoft/winget-pkgs#135148v1.1.1
release job: https://github.com/VirtusLab/scala-cli/actions/runs/7475067612/job/20345017036#step:6:123winget-pckgs
PR: New version: VirtusLab.ScalaCLI version 1.1.1 microsoft/winget-pkgs#133549The text was updated successfully, but these errors were encountered: