Renovate logs

[AdrienLemaire]

What would you like Renovate to be able to do?

I'd like to understand if renovate is aware of some packages upgrades, and why it decided to not create a PR for it.

It clearly seems like many packages should get a PR, and I do not get any renovate error for my config, so wondering if it's a renovate bug or not. Seeing logs would allow me to confirm that.

For reference, here's my renovate config

renovate.json

{
  "assigneesFromCodeOwners": true,
  "automerge": true,
  "dockerfile": {
    "fileMatch": [
      "Dockerfile",
      "^Dockerfile-prod$"
    ]
  },
  "extends": [
    "config:base",
    "schedule:earlyMondays",
    ":preserveSemverRanges"
  ],
  "ignorePaths": [
    "static_src"
  ],
  "labels": [
    "bot"
  ],
  "lockFileMaintenance": {
    "enabled": true,
    "schedule": [
      "before 8am on tuesday"
    ]
  },
  "major": {
    "automerge": false
  },
  "minor": {
    "automerge": true
  },
  "npm": {
    "enabled": true
  },
  "packageRules": [
    {
      "assignAutomerge": true,
      "automerge": true,
      "extends": [
        "schedule:earlyMondays"
      ],
      "updateTypes": [
        "minor",
        "pin",
        "digest"
      ]
    },
    {
      "assignAutomerge": true,
      "automerge": true,
      "extends": [
        "schedule:daily"
      ],
      "updateTypes": [
        "patch"
      ]
    },
    {
      "groupName": "react packages",
      "matchPackageNames": [
        "react",
        "@types/react"
      ],
      "matchPackagePatterns": [
        "react-dom"
      ]
    },
    {
      "groupName": "react router packages",
      "matchPackagePatterns": [
        "react-router"
      ]
    },
    {
      "groupName": "testing packages",
      "matchPackagePatterns": [
        "testing-library",
        "jest"
      ]
    },
    {
      "groupName": "webpack packages",
      "matchPackagePatterns": [
        "webpack"
      ]
    },
    {
      "groupName": "i18n packages",
      "matchPackagePatterns": [
        "i18next"
      ]
    },
    {
      "groupName": "form packages",
      "matchPackagePatterns": [
        "yup",
        "formik"
      ]
    },
    {
      "groupName": "pixi packages",
      "matchPackagePatterns": [
        "pixi"
      ]
    },
    {
      "groupName": "css packages",
      "matchPackagePatterns": [
        "tailwind",
        "postcss",
        "classnames"
      ]
    },
    {
      "excludePackageNames": [
        "ts-transform-graphql-tag"
      ],
      "groupName": "apollo packages",
      "matchPackagePatterns": [
        "apollo",
        "graphql"
      ]
    },
    {
      "excludePackageNames": [
        "eslint-plugin-testing-library",
        "eslint-plugin-i18next",
        "eslint-plugin-graphql"
      ],
      "groupName": "eslint packages",
      "matchPackagePatterns": [
        "^eslint"
      ]
    }
  ],
  "patch": {
    "automerge": true
  },
  "pin": {
    "automerge": true
  },
  "pinDigests": true,
  "pip_requirements": {
    "fileMatch": [
      "requirements.txt",
      "requirements-dev.txt"
    ]
  },
  "prCreation": "not-pending",
  "rangeStrategy": "pin",
  "rebaseWhen": "behind-base-branch",
  "regexManagers": [
    {
      "datasourceTemplate": "docker",
      "fileMatch": [
        "^Dockerfile$"
      ],
      "matchStrings": [
        "ENV [A-Z]+_VERSION=(?<currentValue>.*) # (?<datasource>.*?)/(?<depName>.*?)(\\&versioning=(?<versioning>.*?))?\\s",
        "FROM (?<depName>\\S*):(?<currentValue>\\S*)"
      ],
      "matchStringsStrategy": "any"
    },
    {
      "datasourceTemplate": "npm",
      "depNameTemplate": "node",
      "fileMatch": [
        "^.github/workflows/.*.yml$"
      ],
      "matchStrings": [
        "node-version: \"(?<currentValue>.*?)\""
      ],
      "matchStringsStrategy": "any"
    }
  ],
  "reviewers": [],
  "semanticCommits": "enabled",
  "separateMinorPatch": true,
  "timezone": "asia/tokyo"
}

To summarize:

• Get PRs on Monday
• PRs of similar packages should be grouped
• Get PRs for patch updates if exist.
• Update package-lock on Tuesday.

It's now 10am on Monday, and I got 0 PRs from renovate. But npm outdated returns

➜ npm outdated
Package                                Current        Wanted    Latest  Location                                       Depended by
@apollo/client                           3.3.7         3.3.7    3.3.11  node_modules/@apollo/client                    client
@apollo/react-testing                    3.1.4         3.1.4     4.0.0  node_modules/@apollo/react-testing             client
@babel/core                            7.12.16       7.12.16   7.12.17  node_modules/@babel/core                       client
...
type-fest                               0.20.2        0.20.2    0.21.1  node_modules/type-fest                         client
typescript                               4.1.3         4.1.3     4.1.5  node_modules/typescript                        client
use-callback-ref                         1.2.4         1.2.4     1.2.5  node_modules/use-callback-ref                  client
use-sound                                1.0.2         1.0.2     2.0.1  node_modules/use-sound                         client
webpack                                 5.19.0        5.19.0    5.23.0  node_modules/webpack                           client
yup                                     0.29.1        0.29.1    0.32.9  node_modules/yup                               client

I have patches, minor and major upgrades available.

[viceice]

Please post the debug log.

Which renovate are you using?

You have a lot duplicate automerge configs. Only configure them on package rules.

[AdrienLemaire]

@viceice glad to hear that there are debug logs, that was my question. What do I need to configure in order to see them ?
I'm using the renovate github app, but when searching for "log" or "debug" in the renovate documentation, I can only find matching documents for self-hosted solutions.

[rarkins]

If you've ever received an upgrade PR then the link to the apps log portal is contained there: app.renovatebot.com

[AdrienLemaire]

@rarkins that's awesome, thanks!

Digging a bit in the log, I found that:

• Setting new groups for packages didn't remove existing branches for said packages.
• Having more than 20 branches for renovate prevented renovate from creating new branches for the groups.
  

I do not have prConcurrentLimit set in my config, so it should be 0 (no limit) by default, yet it ends up being 20.

I guess there are 2 problems on renovate's side:

• Renovate should auto-remove branches of packages that are listed in a group
• Renovate shouldn't set prConcurrentLimit: 20 by default.

[viceice]

config:base preset contains the limit