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
HTTPError: Response code 502 (Bad Gateway) #3032
Comments
@yeelimtse Hi, did you able to solve this issue ? I am seeing 502 error during release all of sudden today |
@maheshglm no, have no idea why |
I could resolve the issue in my case, it was due to existing npm project’s package.json , dist and node_modules folders. I tried to run semantic-release excluding them and it was working finally. |
weird, i dont think it's necessary to remove |
Current behavior
In the first release, it successfully analyzed all the commits but it threw a 502 at the end.
Expected behavior
semantic-release passes w/o err.
semantic-release
version22.0.5
CI environment
gitlab-runner 15.4.0, node image: 18.17.1
Plugins used
Installed wi
npx
:semantic-release
configuration.releaserc.yml
CI logs
The text was updated successfully, but these errors were encountered: