How to Troubleshoot Missing Renovate PRs

Issue:

You have enabled Renovate using one of our Developer Integrations and notice that some of your dependencies are not being updated via Renovate.

Troubleshooting:

There are several reasons why Renovate may skip creating a pull request for a dependency.

Check your Renovate configuration for any exclusion rules

You can configure Renovate to ignore certain dependencies using the ‘ignoreDeps’ parameter. First, check to make sure the dependency you are concerned about is not included in the ‘ignoreDeps’ parameter.

You can also specify what types of updates you would like pull requests to be created for, such as patches, minor versions and major versions. Check to make sure that the type of update that you expect is included in your configuration.

To view all configuration options please review the Renovate documentation: https://docs.renovatebot.com/ .

Check your Renovate configuration for any scheduling rules

You can configure Renovate to only open pull requests at certain dates and times and restrict the total number of pull requests that can be created at that time. If you limit the number of pull requests to a number much smaller than the number of dependencies in your project or schedule the pull request generation to be infrequent, you likely will see delays in getting your dependencies' updates.

For example:

CODE

"remediateSettings": {
      "enableRenovate": true,
      "extends": [
        "schedule:monthly",
        ":prHourlyLimit5"
      ],

This configuration schedules PR creation on the 1st of the month between the hours of midnight and 3 AM. Given the time constraints and prHourlyLimit, a maximum of 15 PRs could be created each month. This configuration would be inappropriate for a large project that contains dozens of dependencies.

Confirm that the Scanner and Remediate containers have access to your private registry, if applicable

You can grant Renovate access to your private registries through the following ways:

Copying a .npmrc file (or analogous file for your package manager) into your Docker container through COPY commands within the Dockerfile.
Setting environment variables in the Dockerfile that include the access token or username and password for your private registry.

Note that private registries are not supported for our http://GitHub.com integration.

Confirm that you have set your GitHub Access Token

Setting a GitHub Access Token is required for all Developers Integrations except for http://Github.com . If the token is not provided we will disable creating Renovate pull requests from the GitHub sourced packages, which is essentially anything that you aren't downloading from a private registry. To find more information about setting the token, please review our documentation: Renovate Rate Limiting Errors

If you encounter the following error message in your Remediate logs, you still need to configure your GitHub token: You should configure GITHUB_COM_TOKEN as otherwise the GitHub.com API is heavily rate limited.