Caught error setting branch status

[beyerleinf]

How are you running Renovate?

Self-hosted Renovate CLI

Which platform you running Renovate on?

GitHub.com

Which version of Renovate are you using?

43.233.4

Please tell us more about your question or problem

Renovate seems to encounter an error when setting the branch status, failing the entire run for the repo. I'm running as a GitHub App and have set the permissions according to the docs.

Logs (if relevant)

Logs

DEBUG: Updating renovate/stability-days status check state to green (repository=[org]/[repo], branch=renovate/axllent-mailpit-1.x)
DEBUG: Setting branch status (repository=[org]/[repo], branch=renovate/axllent-mailpit-1.x)
       "context": "renovate/stability-days",
       "state": "green"
DEBUG: POST https://api.github.com/repos/[org]/[repo]/statuses/8165fb69208bc670b2e49ede8df1526bc60075b8 = (code=ERR_NON_2XX_3XX_RESPONSE, statusCode=422 retryCount=0, duration=208) (repository=[org]/[repo], branch=renovate/axllent-mailpit-1.x)
DEBUG: Caught error setting branch status - aborting (repository=[org]/[repo], branch=renovate/axllent-mailpit-1.x)
       "err": {"message": "err.body?.errors?.find is not a function"},
       "url": "repos/[org]/[repo]/statuses/8165fb69208bc670b2e49ede8df1526bc60075b8"
       TypeError: err.body?.errors?.find is not a function
           at handleGotError (file:///usr/local/renovate/lib/util/http/github.ts:183:34)
           at GithubHttp.handleError (file:///usr/local/renovate/lib/util/http/github.ts:383:11)
           at GithubHttp.request (file:///usr/local/renovate/lib/util/http/http.ts:272:12)
           at processTicksAndRejections (node:internal/process/task_queues:104:5)
           at GithubHttp.requestJsonUnsafe (file:///usr/local/renovate/lib/util/http/github.ts:397:20)
           at GithubHttp.requestJson (file:///usr/local/renovate/lib/util/http/http.ts:388:17)
           at Proxy.setBranchStatus (file:///usr/local/renovate/lib/modules/platform/github/index.ts:1320:5)
           at setStatusCheck (file:///usr/local/renovate/lib/workers/repository/update/branch/status-checks.ts:56:5)
           at setStability (file:///usr/local/renovate/lib/workers/repository/update/branch/status-checks.ts:109:3)
           at setBranchStatusChecks (file:///usr/local/renovate/lib/workers/repository/update/branch/index.ts:64:3)
           at processBranch (file:///usr/local/renovate/lib/workers/repository/update/branch/index.ts:779:5)
           at instrument.attributes (file:///usr/local/renovate/lib/workers/repository/process/write.ts:188:21)
           at writeUpdates (file:///usr/local/renovate/lib/workers/repository/process/write.ts:161:17)
           at update (file:///usr/local/renovate/lib/workers/repository/process/extract-update.ts:304:11)
           at renovateRepository (file:///usr/local/renovate/lib/workers/repository/index.ts:142:21)
           at instrument.attributes (file:///usr/local/renovate/lib/workers/global/index.ts:235:11)
           at start (file:///usr/local/renovate/lib/workers/global/index.ts:220:7)
           at file:///usr/local/renovate/lib/renovate.ts:26:22
DEBUG: Passing repository-changed error up (repository=[org]/[repo], branch=renovate/axllent-mailpit-1.x)
 INFO: Repository has changed during renovation - aborting (repository=[org]/[repo])
DEBUG: Repository result: repository-changed, status: onboarded, enabled: true, onboarded: true (repository=[org]/[repo])           

[krotname]

There are two separate things in that log.

The real failure is the line before the TypeError:

POST /repos/[org]/[repo]/statuses/8165fb... = statusCode=422

So Renovate is trying to create the renovate/stability-days commit status for that branch commit. For a GitHub App, the Renovate docs list Commit statuses: read and write as a required permission. Make sure the App has that permission on the installation, not only Checks/Contents/Pull requests, and re-approve/reinstall the app if you changed permissions after installation.

The err.body?.errors?.find is not a function part looks secondary: in Renovate's GitHub HTTP error handling, the 422 branch assumes errors is an array. Your GitHub response seems to have a different body shape, so Renovate masks the useful GitHub error message.

If the Commit statuses permission is already definitely read/write, the next thing I would check is whether that exact SHA still exists in the repo when Renovate posts the status. A 422 from the statuses endpoint can also happen when GitHub rejects the target SHA/request as invalid. Running once with trace logging or capturing the raw 422 response body would be the useful data for a Renovate bug report, because the current stack trace hides it.

[Nisden]

How do you get Renovate to log the response body? Because I am seeing the same issue (on a fresh install I just made yesterday)

[beyerleinf]

Renovate keeps OOMing when running with TRACE log level, still working it out

[beyerleinf]

Interestingly enough, I updated Renovate to 43.235.1 today and the issue no longer appears 🤔

[jamietanna]

Yep, this was fixed in https://github.com/renovatebot/renovate/releases/tag/43.234.1 - apologies for the breakage