502 Bad Gateway errors when fetching merge commits on main branch (original) (raw)

Thanks for stopping by to let us know something could be better!

Please provide the following details.

Environment details

Steps to reproduce

We are seeing intermittent failures in our CI when release-please attempts to fetch merge commits on the main branch.
The error occurs before a release PR is opened, and happens even after changing to a different self-hosted runner.

Run googleapis/release-please-action@v4 in a GitHub Actions workflow on a repository with an existing

 Run googleapis/release-please-action@v4

Running release-please version: 17.1.2
✔ Looking for latest release on branch: main with prefix: 
❯ Fetching merge commits on branch main with cursor: undefined
✔ received 502 error, 5 attempts remaining
✔ received 502 error, 4 attempts remaining
✔ received 502 error, 3 attempts remaining
✔ received 502 error, 2 attempts remaining
✔ received 502 error, 1 attempts remaining
⚠ ran out of retries and response is required
Error: release-please failed: <html>
<head><title>502 Bad Gateway</title></head>
<body>
<center><h1>502 Bad Gateway</h1></center>
<hr><center>nginx</center>
</body>
</html>

First Occurrence back when this was submitted #2577. Started again yesterday and is intermittent