-
Notifications
You must be signed in to change notification settings - Fork 118
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
Publish step returns 406, but tag was pushed to repo #161
Comments
What GHE version is it? I’m not 100%, but a 406 response suggest a problem with the accept header I think? The request that cause the 406 is
Could you check with support@github.com if they have an idea? Send the the request above along with the GHE version |
@gr2m Thanks for the response. Will check with GH support and share what I find here. |
Closing as no feedback was provided. Please re-open if the issue persist and provide the info requested. |
I've also faced with this issue. In my case it was related to header handling and fixed by adding proper context path to GH_URL. |
Has anyone contacted support about this? |
I'm seeing an unexpected behavior during the publish step. I'm running a Jenkins job against Enterprise github. semantic-release is calculating the correct version based on the commit message and pushes a tag. GH responds with 406, the build fails, but the tag is successfully pushed to the repo.
What I understand 406 "Not Acceptable" to be is response given in place of a more cryptic one.
I can successfully generate and push a tag via the Jenkins job with git commands. Any ideas what the issue might be?
Config
Job log
The text was updated successfully, but these errors were encountered: