Renovate: [Question] Invalid configuration option: default

Created on 25 Jun 2019  路  7Comments  路  Source: renovatebot/renovate

Which Renovate are you using? CLI, App, or Pro

CLI (renovate/renovate container on GKE, self-hosted)

Which platform are you using? GitHub, GitLab, Bitbucket Azure DevOps

Github

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

What is your question?

Renovate is working correctly, but the bot account is leaving the following comment on all human-created PRs in our configuration repository (the one that pushes our shareable config to NPM):

Renovate Configuration Errors
package.json: Invalid configuration option: default

I am able to validate the config locally just fine. Any idea if I'm missing something?

priority-3-normal

Most helpful comment

I'm not sure why this is happening so working on an option to at least suppress the behaviour. Moving this issue to the main repo as it requires code changes

All 7 comments

Can you share the relevant sections of your package.json?

yep:

{
  "name": "org",
  "version": "1.2.1",
  "scripts": {
    "validate": "renovate-config-validator"
  },
  "renovate-config": {
    "default": {
      "extends": [
        "config:base",
        ":preserveSemverRanges",
        ":rebaseStalePrs",
        ":semanticCommits",
        ":semanticCommitTypeAll(chore)",
        ":prHourlyLimit4"
      ],
      "major": {
        "enabled": true,
        "schedule": "before 6am on the first day of the month"
      },
      "prConcurrentLimit": 3,
      "schedule": [
        "before 6am every weekday"
      ],
      "rangeStrategy": "bump",
      "dockerfile": {
        "enabled": true
      },
      "bundler": {
        "enabled": true
      },
      "packageRules": [
        {
          "packageNames": [
            "renovate",
            "renovate/renovate"
          ],
          "groupName": "renovatebot",
          "separateMajorMinor": false,
          "separateMinorPatch": false,
          "schedule": "at any time"
        },
        {
          "depTypeList": [
            "dependencies"
          ],
          "semanticCommitType": "fix"
        },
        {
          "depTypeList": [
            "devDependencies"
          ],
          "groupName": "devDependencies",
          "separateMajorMinor": false,
          "separateMinorPatch": false
        }
      ],
      "patch": {
        "groupName": "patchReleases"
      },
      "separateMinorPatch": true
    }
  },
  "dependencies": {},
  "devDependencies": {
    "renovate": "^18.16.13"
  }
}

Do you also have a renovate.json in the same repo?

we do, the contents of which are:

{
  "extends": [
    "@org"
  ]
}

it was created by the onboarding PR. i'm guessing this is where the conflict lies? would deleting it help or would that trigger another onboarding attempt?

I'm not sure why this is happening so working on an option to at least suppress the behaviour. Moving this issue to the main repo as it requires code changes

thank you @rarkins!

closing this since adding "suppressNotifications": ["prValidation"] seemed to work. thanks!

Was this page helpful?
0 / 5 - 0 ratings