How can I find out why Renovate closes the Pull Request?

[emmenko]

Which Renovate are you using?

WhiteSource Renovate App

Which platform are you using?

GitHub.com

Have you checked the logs? Don't forget to include them if relevant

I tried but it keeps showing me the "Please authenticate" page. 🤷‍♂️

What would you like to do?

Recently I noticed that the (scheduled) Pull Request opened by Renovate suddenly gets closed, and I can't figure out the reason why is that. Even if I manually reopen it, it then gets closed again.

For example:

Any help would be appreciated, thanks.

[emmenko]

Ping

[rarkins]

Renovate generally doesn't "know" why a PR needs closing - it just knows which PRs should exist, and closes any that shouldn't (unless you disable that feature and clean up PRs yourself).

Sometimes it can occur because a datasource was unavailable temporarily, and was not treated as an essential "datasource failure" to abort the run. In such cases you should expect to see a new PR opened once the datasource responds the next time.

If you compare the debug logs between runs then the differences may give you a hint as to why it wasn't kept open. If the dashboard still isn't working for you then please raise that as a separate issue in https://github.com/renovatebot/app-support

[emmenko]

Thanks for the feedback. The weird thing is that recently it seems to happen "consistently" across some of our repositories.
Also from the screenshot above you can see that when the ZEIT Now (Vercel) deployments failed, the PR got closed by the Renovate bot. Was it just a coincidence?

If the dashboard still isn't working

Tried again, it's working now 👌

[rarkins]

Was it just a coincidence?

I would think it's just a coincidence, but things like this have surprised me before. I recommend:

• Look at the exact time stamp for when it was autoclosed
• Match that timestamp against the logs in the dashboard to find the right job
• Look at that job's logs for that branch
• If still unclear, download and compare the job's logs with the job before it, as hopefully that might give a hint

[emmenko]

Alright, thanks a lot for the feedback. I'll try to find out more in the logs when I have some time.

[emmenko]

@rarkins Hi, so I've been trying to look at the logs, as Mondays we have the scheduled update and the issue this occurs.

I'm starting to wonder if the problem is somehow related to having a scheduled update time. In the logs I see this:

Does not match schedule because 63391 is later than 18000

I can't find any other useful logs that might explain the behavior.

I could try removing the schedule and observe if the issue still occurs. Do you think it would help?

PS: my renovate config is like this

{
  "extends": [
    "config:base",
    ":pinOnlyDevDependencies",
    "schedule:weekly"
  ],
  "separateMajorMinor": true,
  "groupName": "all dependencies",
  "groupSlug": "all",
  "packageRules": [
    {
      "packagePatterns": [
        "*"
      ],
      "groupName": "all dependencies",
      "groupSlug": "all"
    }
  ],
  "lockFileMaintenance": {
    "enabled": true
  },
  "labels": ["🤖 Type: Dependencies"],
  "ignoreDeps": []
}

[rarkins]

That log doesn't show any Pull Request being closed, does it? I can't search it easily because it's a screenshot

[emmenko]

Example PR: commercetools/commercetools-docs-kit#432

Logs: https://app.renovatebot.com/dashboard#github/commercetools/commercetools-docs-kit/175489642

This one maybe? (I admit I'm a bit confused to what I should look for)

[rarkins]

Seems that something is going wrong with the mix of lockFileMaintenance. Here's what I suggest for your config:

{
  "extends": [
    "config:base",
    ":pinOnlyDevDependencies",
    "schedule:weekly"
  ],
  "separateMajorMinor": true,
  "packageRules": [
    {
      "packagePatterns": [
        "*"
      ],
      "updateTypes": ["minor", "patch"],
      "groupName": "all dependencies",
      "groupSlug": "all"
    }
  ],
  "lockFileMaintenance": {
    "enabled": true
  },
  "labels": ["🤖 Type: Dependencies"],
  "ignoreDeps": []
}

[rarkins]

BTW I am also removing the rule that seems to be misfiring for you. But I recommend you don't combine major updates into that all updates.