renovatebot / renovate

Home of the Renovate CLI: Cross-platform Dependency Automation by Mend.io
https://mend.io/renovate
GNU Affero General Public License v3.0
17.14k stars 2.23k forks source link

Github App not creating PRs after configuration branch is merged #3545

Closed dpikt closed 5 years ago

dpikt commented 5 years ago

I added Renovate to a private repository and merged the configuration branch, after changing the config file a bit. In the body of the PR, it said:

With your current configuration, Renovate will create 10 Pull Requests.

But I merged it a few days ago and no new pull requests have appeared. The only change I made to the branch was a version bump in my package.json and edits to the config resulting in the following:

{
  "extends": [
    "config:base"
  ],
  "bumpVersion": "patch",
  "minor": {
    "enabled": false
  },
  "patch": {
    "enabled": false
  },
  "pin": {
    "enabled": false
  },
  "prHourlyLimit": 0
}

Any ideas on how to troubleshoot this? Thanks!

rarkins commented 5 years ago

Can you email the repo name to support@renovatebot.com so I can look it up? Or mention it here if it’s not a secret

dpikt commented 5 years ago

Sure thing, it's LaunchPadLab/client-template. Thanks for the quick response!

rarkins commented 5 years ago

This is an interesting edge case. First of all, if you go to https://renovatebot.com/dashboard you can see that Renovate has been running regularly for this repo. You can see it expects to create 11 branches but then they all report something like Branch renovate/bourbon-5.x is blocked by a Pin PR.

Renovate holds back upgrades for any dependency where there is also a pin PR pending. But in your case you've suppressed the pin PR so it's an unfortunate standoff. If you add the preset :preserveSemverRanges to your extends array then it should stop any pin PRs from being created in the first place, hence nothing to suppress, and then nothing to block upgrades.

dpikt commented 5 years ago

@rarkins I'll give that a shot. Thank you!