Renovate failed to generate composer.lock No tool releases found with self-hosted Renovate in Kubernetes

[Geni2]

How are you running Renovate?

Self-hosted Renovate

Which version of Renovate are you using?

renovate/renovate:41.151.0

41.151.0 (2025-10-16)

Code Repository

Bitbucket server v7.21.21

Please tell us more about your question or problem

Self-hosted Renovate in Kubernetes fails to generate composer.lock files with error "No tool releases found" despite trying multiple binarySource configurations.

To Reproduce
Environment:

Renovate version: 41.151.0
Platform: Bitbucket Server (self-hosted)
Deployment: Kubernetes with ConfigMap
Base image: renovate/renovate:41
Configuration:

ConfigMap

module.exports = {
  platform: "bitbucket-server",
  endpoint: "https://bitbucket.xxx.xxx",
  binarySource: 'install', // Also tried 'docker' and 'global'
  enabledManagers: ['composer'],
  lockFileMaintenance: { enabled: true },
  repositories: ['repo/name']
};

Logs (if relevant)

Logs

DEBUG: Failed to generate composer.lock (repository=repo-name)
2025-11-21 07:14:19.587 |        "err": {
2025-11-21 07:14:19.587 |          "message": "No tool releases found.",
2025-11-21 07:14:19.587 |          "stack": "Error: No tool releases found.\n 

[github-actions[bot]]

Hi, please format any copy/pasted code or logs so they're readable.

You can read a Markdown code formatting guide as well as some GitHub-specific information formatting code blocks.

Thanks, the Renovate team

[jamietanna]

Can you please also specify exactly which Renovate 41 version you're using?

[Geni2]

Hi @jamietanna , here is the full logs: https://gist.github.com/Geni2/1460e48c10114ee510764e91541bd1d9. Please let me know if you can't open it

[jamietanna]

@Geni2 can you please share logs when you have binarySource=install, as that was what the original request was for?

(Via binarySource=docker isn't recommended in most cases)

[jamietanna]

That being said, if we look around the No tool releases found:

DEBUG: GitHub failure: rate limit (repository=PLATFORM/reponame1, branch=maintenance-pipeline-100-major-all-deps)
       "err": {
         "name": "HTTPError",
         "code": "ERR_NON_2XX_3XX_RESPONSE",
         "timings": {
           ...
         },
         "message": "Response code 403 (rate limit exceeded)",
         "stack": "HTTPError: Response code 403 (rate limit exceeded)\n    at Request.<anonymous> (/usr/local/renovate/node_modules/.pnpm/[email protected]/node_modules/got/dist/source/as-promise/index.js:118:42)\n    at processTicksAndRejections (node:internal/process/task_queues:105:5)",
         "options": {
           "headers": {
             "user-agent": "RenovateBot/41.151.0 (https://github.com/renovatebot/renovate)",
             "accept": "application/json, application/vnd.github.v3+json",
             "content-type": "application/json",
             "content-length": "652",
             "accept-encoding": "gzip, deflate, br"
           },
           "url": "https://api.github.com/graphql",
           "hostType": "github-releases",
           "username": "",
           "password": "",
           "method": "POST",
           "http2": false
         },
         "response": {
           "statusCode": 403,
           "statusMessage": "rate limit exceeded",
           "body": {
             "message": "API rate limit exceeded for 83.137.191.1. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)",
             "documentation_url": "https://docs.github.com/rest/overview/resources-in-the-rest-api#rate-limiting"
           },
           "headers": {
             ...
           },
           "httpVersion": "1.1",
           "retryCount": 0
         }
       }
DEBUG: Datasource unknown error (repository=PLATFORM/reponame1, branch=maintenance-pipeline-100-major-all-deps)
       "datasource": "github-releases",
       "packageName": "containerbase/php-prebuild",
       "err": {
         "message": "rate-limit-exceeded",
         "stack": "Error: rate-limit-exceeded\n ..."
       }
 WARN: No tool releases found. (repository=PLATFORM/reponame1, branch=maintenance-pipeline-100-major-all-deps)
       "toolConfig": {
         "datasource": "github-releases",
         "packageName": "containerbase/php-prebuild",
         "versioning": "composer"
       }
DEBUG: Failed to generate composer.lock (repository=PLATFORM/reponame1, branch=maintenance-pipeline-100-major-all-deps)
       "err": {
         "message": "No tool releases found.",
         "stack": "Error: No tool releases found.\n  ..."
       }

[jamietanna]

It looks like you're not setting a GITHUB_COM_TOKEN (see also: #39406) so Renovate isn't authenticating to GitHub, and you're getting rate limited

Specifying one will allow Renovate to access with a much higher rate limit

[Geni2]

Hi @jamietanna , thank you very much for your response. I will have a look today to set the GITHUB_COM_TOKEN, and then I will see.
But will this solve my issue with composer.lock?

[jamietanna]

I believe so - the error above indicates that composer.lock isn't being updated because you're not authenticated to GitHub (to download PHP)

But if not, please let us know in this Discussion :)

[Geni2]

Hi @jamietanna , indeed, as you said that solved the issue with composer lock and now it's showing another error related to composer update:

"lockFile": "pimcore/composer.lock",
"stderr": "Command failed: composer update

[jamietanna]

Can you please share more of the context from that error? I can't help without much more info

[github-actions[bot]]

Hi there,

This issue or discussion is missing some logs, making it difficult or impossible to help you. Depending on which situation applies follow one, some or all of these instructions.

No logs at all

If you haven't posted any log yet, we need you to find and copy/paste the log into the issue template.

Finding logs on hosted app

Select me to read instructions

If you use the Mend Renovate app (GitHub):

1. Log in to the Mend Developer Portal
2. Navigate to the correct organization and repository
3. Locate the appropriate log (it may not always be the latest one)
4. Copy/paste the log contents
5. Follow the steps in the formatting your logs section

Finding logs when self-hosting

Select me to read instructions

Read the Renovate docs, troubleshooting, self-hosted to learn how to find the logs.

Formatting your logs

Select me to read instructions

Please put your logs in a <details> and <summary> element like this:

<details><summary>Select me to see logs</summary>

```
Copy/paste your logs here, between the starting and ending backticks
```

</details>

If you feel the logs are too large to paste here, please use a service like GitHub Gist and paste the link here.

Good luck,

The Renovate team