Renovate exits because of "token is not a valid HTTP header" response from Github API #29626
-
What would you like help with?I think I found a bug How are you running Renovate?Self-hosted If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.Gitlab platform, Renovate version 37.399.8 Please tell us more about your question or problemWe started trying to use the I thought this might be similar to #26991 and may need similar changes to fix it, but I'm not sure. Logs (if relevant)Logs
|
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
-
@rarkins apologies, I found similar errors for For anyone in the future running into similar error messages, check the secret you're passing to |
Beta Was this translation helpful? Give feedback.
@rarkins apologies, I found similar errors for
ERR_INVALID_CHAR
when calls were being made to Github to get Changelogs, it's just that those errors didn't cause the process to fail and exit so we hadn't noticed them.For anyone in the future running into similar error messages, check the secret you're passing to
GITHUB_COM_TOKEN
to see if any newline characters are present