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
GITHUB_COM_TOKEN will not be used to download presets #11496
Comments
Please provide the full (redacted) logs from startup to error |
|
Do you know where the |
Honestly, I do not have a clue.
I guess one of the presets is referencing it. |
@viceice can you figure it out? I don't see it in our source code: |
I guess he's using our https://gitlab.com/renovate-bot/renovate-runner templates ? |
Aye. That's where it' coming from. |
I guess we need to do a hostRules.add() call before resolving presets |
Just a minor update, the preset resolvement also ignores hostRules that are set explicitly. |
Its not only the preset fetching, somehow also dependency checks are running into zthe rate limit now (as unauthenticated
|
Something is really strange... With |
How are you running Renovate?
Self-hosted
Please select which platform you are using if self-hosting.
GitLab self-hosted
If you're self-hosting Renovate, tell us what version of Renovate you run.
26.13.8
Describe the bug
In the documentation, it is mentioned to set GITHUB_COM_TOKEN to a private access token to get around the problems with rate limits. This does not work.
I suspect the following line:
https://github.com/renovatebot/renovate/blob/main/lib/config/presets/github/index.ts#L13
No options are set here.
Relevant debug logs
Logs
Have you created a minimal reproduction repository?
No reproduction repository
The text was updated successfully, but these errors were encountered: