I just received this issue from renovate on one repo where I have it enabled:

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: Preset name not found within published preset config (monorepo:babel6). Note: this is a nested preset so please contact the preset author if you are unable to fix it yourself.

I don't have any custom preset configuration in my config, so I assume that something broke in Renovate presets. Any idea?

A follow up to mend/renovate-ce-ee#11

I am setting RENOVATE_NPMRC to registry=http://artifactory.example.com/artifactory/api/npm/npm/\n@scope:registry=http://artifactory.example.com/artifactory/api/npm/npm-scope/

Renovate seems to get the registry configuration value correctly, but the @scope:registry property is not set. Therefore, all requests for @scope packages are failing.

I thought, based on another issue I saw, that the newline would allow Renovate to correctly re-create the .npmrc file when it contains two more or more lines.

Should disable node managers as well as node engines and docker node

With #181 I've introduced mono repos for Arcus but it turns out I've probably misconfigured them given they are not respected.

Based on https://github.com/renovatebot/presets/blob/master/packages/renovate-config-monorepo/generate.js#L12 I would expect all of the packages from there to be updated in parallel.

However, multiple of them are opened:

We don't use that extensive configuration : https://github.com/arcus-azure/arcus.templates/blob/master/renovate.json#L10

/cc @stijnmoreels

Based on our earlier discussion. :)

I'd like to put up a config preset for small focused package, aka micro packages. What defines these packages is that they don't need much maintenance and only have a few dependencies. This translates to no version pinning, grouping of all dependencies and a monthly schedule:

{
  "pinVersions": false,
  "groupName": "all",
  "schedule": ["before 8am on the first day of the month"],
  "lockFileMaintenance": {
    "schedule": ["before 8am on the first day of the month"]
  }
}

Instead of opening a PR I'm opening this issue because I'm not sure where to put such a config in the current directory structure. Correct me if I'm wrong, no directory/category seems to fit the above unless split.

Will be great 👍

It's not a monorepo, but there are parts of it that are loosely coupled.

https://github.com/semantic-release

So for example the @semantic-release/git type is tied to the normal semantic-release dependency. Ideally, group anyting with "semantic-release` in the name into a single PR as they probably need to move together anyway.

would love to have a JSON schema (as an npm package) to use for validating our custom config as part of our build and release process.

the npm package should just expose the JSON schema itself, and users can adopt any JSON Schema testing tool to run the validation

Hey, I've just noticed that the production dependencies got pinned for some of our repos.

The renovate config for one of those repositories is:

{
  "extends": [
    "@ht2-labs:base"
  ]
}

That config extends our base config which is this:

{
  "extends": [
    ":library"
  ],
  "automerge": true,
  "automergeType": "branch-push",
  "major": {
    "automerge": false
  }
}

I've noticed that the :library config appears to be deprecated in here, so I'm guessing I need to change to the config:js-lib config, however, the :library config does currently extend the config:js-lib so I'm not sure if that's going to work. I will try that anyway when I get a minute, I think I'll also need to manually unpin the pinned prod dependencies so it might take a little while.

I'd like to configure my repos to update @fortawesome dependencies in bulk, but I'm struggling to understand how to make it happen. Can someone show me how this is supposed to work?

My dependencies are:

"@fortawesome/angular-fontawesome": "0.1.0-7",
"@fortawesome/fontawesome-free-brands": "5.0.10",
"@fortawesome/fontawesome-pro-light": "5.0.10",
"@fortawesome/fontawesome-pro-regular": "5.0.10",
"@fortawesome/fontawesome-pro-solid": "5.0.10",
"@fortawesome/fontawesome-svg-core": "1.2.0-11",

Thanks!

Ideally each PR should be validated to make sure it passes.

I've tried to add an NPM token following the instructions "Add an encrypted npm token to repository" however my onboarding PR is still giving me warnings about private packages e.g. @trussle/package-name.

Is this incorrectly configured or does the onboarding PR not clear these warnings? I've tried issuing other tokens and using the encode the .npmrc file options also, but still see the warning message in the onboarding PR.

renovate.json

{
  "extends": ["config:base"],
  "minor": {
    "groupName": "minor"
  },
  "docker": { "enabled": false },
  "encrypted": {
  "npmToken":  ""
  }
}

List of packages
https://github.com/vuejs/vue-cli/tree/dev/packages/%40vue
They are released like this:
https://www.npmjs.com/package/@vue/eslint-config-prettier

We're receiving a report for Action Required: Fix Renovate Configuration in the following issue - conventional-changelog/conventional-changelog#302

I threw the JSON file into a JSON validator and it passes.

It's also the exact same file as we use for releaser-rools.

Hello,

I saw an update to the Next.js monorepo definition recently, but somehow next and next-server upgrades still occur separately:

Can we group them please?

Hi,

I just started using Renovate and the doc about the allowed types for automergeType is a bit confusing. It says that the allowed values are: branch,pr,pr-comment, but the preset uses two other values:

• branch-merge-commit
• branch-push

Are those values outdated?, how do they work?

Current entry:

    "graphqlcodegenerator": {
      "description": "graphqlcodegenerator monorepo",
      "packageNames": [
        "graphql-code-generator",
        "graphql-codegen-core"
      ]
    },

It only picks up the 2 packages from the top level of packages, not the ones in packages/*/*/package.json (like all the packages in https://github.com/dotansimha/graphql-code-generator/tree/master/packages/plugins)

The entry was added in #45.

I tried to put together a PR, but I'm not sure how to provide pattern it should glob? Looking at the code, it seems I can just provide a single string path

In our initial PR (mozilla/treeherder#3025), the example commit messages contain the fix(deps) prefixes, even though we don't use semantic commits. This was initially confusing, since looking at the config docs, the default for semanticCommits is null (from here) which is auto-detect, which presumably should have turned off the prefixes for us.

I'm guessing that since the PR is using config:base, the included :semanticPrefixFixDepsChoreOthers preset is overriding the auto-detect behaviour to always enable semantic commit messages?

Presuming that's the case:

1. Should config:base instead maintain the auto-detect behaviour?
2. Is there a simple way to override the current config:base usage of :semanticPrefixFixDepsChoreOthers? Looking at the source (here) it seems I'd have to override x4 (one for each of dep/devDeps/...)

Many thanks :-)

Spring is a Java framework available through Maven Central on Maven and Gradle.
https://github.com/spring-projects/spring-framework
https://mvnrepository.com/artifact/org.springframework

Spring has several groupings

When attempting to generate the source for monorepo configuration I get the following error:

node generate
internal/modules/cjs/loader.js:628
    throw err;
    ^

Error: Cannot find module '@sindresorhus/is'
Require stack:
- .../renovatebot/presets/packages/renovate-config-monorepo/generate.js
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:625:15)
    at Function.Module._load (internal/modules/cjs/loader.js:527:27)
    at Module.require (internal/modules/cjs/loader.js:683:19)
    at require (internal/modules/cjs/helpers.js:16:16)
    at Object.<anonymous> (.../renovatebot/presets/packages/renovate-config-monorepo/generate.js:1:12)
    at Module._compile (internal/modules/cjs/loader.js:776:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:787:10)
    at Module.load (internal/modules/cjs/loader.js:643:32)
    at Function.Module._load (internal/modules/cjs/loader.js:556:12)
    at Function.Module.runMain (internal/modules/cjs/loader.js:839:10) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    '.../renovatebot/presets/packages/renovate-config-monorepo/generate.js'
  ]
}

Not the only user getting this error as @tomkerkhove also reported it here, #169

Remove direct references to dependencies, devDependencies and peerDependencies

This is a monorepo for a Spring-based API documentation tools. Please see PR #141

Hi!

I see there is grouping support for Angular (as in v2+):
https://github.com/singapore/renovate-config/blob/dbe6d310deeb47be1438a28394fcbc386ffa7171/packages/renovate-config-monorepo/package.json#L12-L15
https://github.com/singapore/renovate-config/blob/dbe6d310deeb47be1438a28394fcbc386ffa7171/packages/renovate-config-group/package.json#L19-L27
https://github.com/singapore/renovate-config/blob/dbe6d310deeb47be1438a28394fcbc386ffa7171/packages/renovate-config-group/package.json#L71

The mozilla/treeherder project (mozilla/treeherder#3025) still uses Angular.js (as in v1; 😭), which doesn't currently have grouping support enabled - though does have these package names defined:
https://github.com/singapore/renovate-config/blob/dbe6d310deeb47be1438a28394fcbc386ffa7171/packages/renovate-config-packages/package.json#L12-L20

Would there be any objection to enabling grouping for the packages listed here?
https://github.com/angular/angular.js/blob/master/scripts/bower/repos.inc
(which matches the names here: https://code.angularjs.org/1.6.6/)

Avoid needing to publish own to nom

e.g. group depends on monorepo

https://github.com/guigrpa/oao

The following config options were renamed in renovatebot/renovate#1952

• multipleMajorPrs => separateMultipleMajor (false)
• separateMajorReleases => separateMajorMinor (true)
• separatePatchReleases => separateMinorPatch (false)

It looks like the default preset has not been updated and still sets the old config option names:

• separateMajorReleases
• separatePatchReleases
  https://github.com/renovatebot/presets/blob/5108b129a99d61a050507e98730c001591a1948a/packages/renovate-config-default/package.json#L93:L100

The Documentation has been updated to reference only the new config options:
https://renovatebot.com/docs/configuration-options/#separatemajorminor

I am not entirely sure that I understand how this is working, but it seems that the presets need to be migrated to the new config name. If yes, how do you prefer to migrate this change?

I see the following options:

A

• Rename the preset to match the new config names separateMajorMinor, separateMinorPatch, and change the config option to match
• Change renovate-config-base to reference the new preset names
• This will break anyone who’s directly referencing the old preset names

B

• Add a new preset with the new config names separateMajorMinor, separateMinorPatch and matching config options
• Leave the old preset names separateMajorReleases and separatePatchReleases in place, and change the config options set to separateMajorMinor and separateMinorPatch, to not break people referencing them directly

Thanks!

I'm getting an issue from renovatebot that says Preset name not found within published preset config (group: allNonMajor). I have been using this preset successfully in other repos.

I'm using forking-renovate. This is the configuration file - https://github.com/firebase/firebase-js-sdk/blob/master/renovate.json

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

Looking forward to use Renovate App, but not yet merged the first PR.

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

GitHub organization with public repositories in becoming.

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

Not yet, as I haven't installed it yet.

Context

So, I'm currently creating a Yeoman opinionated project to handle scaffolding and syncing config files, carrying redundant tasks on my behalf across all the future repositories.

I first wired Greenkeeper to benefit from dependencies PR updates, but looking at your project it looks very interesting.

I planned to use Travis and Renovate to build CI/CD automation.

What is your question?

I currently use Gitmoji based semantic release, which I enjoy a lot more than classic semantic conventions.

To be able to do so, I use semantic-release / semantic-release-gitmoji / commitlint / commitlint-config-gitmoji / some other projects on top of which I setup custom configurations.

Sample can be found here, README isn't complete yet though.

All my automated semantic releases rely on a commit template like so :

:emoji: Some title

Facultative message body

Facultative extras like : #1

Finally my question is easy : can I for example setup commitMessagePrefix depending on commitMessageAction that :

• Update add :arrow_up: prefix to the title
• Pin add :pushpin: prefix to the title
• Roll back add :arrow_down: prefix to the title
  ... and so on ?

Thanks in advance ^^

Can we switch to yarn instead of npm for package references?

I have Renovate configuration package with a package.json file that contains the following configuration section:

{
  "renovate-config": {
    "default": {
      "extends": [
        "config:base"
      ]
    }
  }
}

When I run yarn renovate-config-validator I get the following error:

yarn run v1.5.1

Validating renovate.json
renovate.json is not valid JSON
Validating package.json > renovate-config
error An unexpected error occurred: "Command failed.
Exit code: 1

I went as far as having an package.json file with just the renovate-config section, but I still get the same error.

I can confirm that I started getting the validation error with version 11.40.0. though I still receive the error in Renovate 11.44.1.

Sometimes the amount of devDependencies is just too much, I think it would be good to have the option of disable Renovate for devDependencies.

PR: #80

Hibernate is a Java framework available through Maven Central on Maven and Gradle.
http://hibernate.org
https://mvnrepository.com/artifact/org.hibernate

Hibernate has several groupings

I created a preset of my own to enable me to group unit test related packages just like linter-packages can be grouped through the official presets.

The configuration can be found here: https://github.com/voxpelli/renovate-config-voxpelli/blob/master/package.json

An example of a PR can be found here: voxpelli/node-jekyll-utils#13

I have made no attempt to list all unit test related javascript packages, but rather listed the one I know I use across my projects

Update: Feel free to include these among the other official groups you have in here if you like 🙂

Should angular cli be a monorepo? The release several packages from the cli repo.

Major linter upgrades almost always break builds, but non-major ones should almost never do it.

Having a linters group limited to non-majors, like the testNonMajor, would be neat 👍

(Btw: Apart from my personal testing of your GitHub app, we're also trialing it internally at @Sydsvenskan now – works nicely so far 🎉)

Let's refactor this repo to be simpler and use github presets instead of a publishing step.

Hi,

Here is a mono repo that I'm using: https://github.com/accounts-js/accounts

How should I config the monorepo in my renovate.json config?
How could I add this directly in your preset so that everyone benefit from the config?

Thx

The preset sets ignorePaths to an empty array, which means both of the default elements ([‘/node_modules/’, ‘/bower_components/’]) are removed, rather than just node_modules:
https://renovateapp.com/docs/configuration-reference/configuration-options#ignorepaths
https://github.com/singapore/renovate-config/blob/1ad87fa442859eea25768a751e5ca3e93692f59d/packages/renovate-config-default/package.json#L24-L27

Perhaps the simplest way to solve this is just to change the preset description to clarify it affects both?

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

File: renovate.json
Error type: The renovate configuration file contains some invalid settings
Message: Invalid regExp for packageRules[0].packagePatterns: eslint,prettier``

socket.io and socket.io-client would be main offenders, they share version number and release at the same time. I'm unsure if other socket.io repos can also apply.

Is it possible to define custom schedule by defining a custom interval for the updates? We're currently using after 9pm on sunday, so would something like after 9pm every second sunday work?

I've tried setting up one of our larger services today to use renovate. Using the config:base option we'd end up with ~35 initial PRs so I was looking to tweak the settings to create larger PRs that group minors and patch versions.

Looking over the configuration I decided on the following;

{
  "extends": ["config:base"],
  "combinePatchMinorReleases": true,
  "separatePatchReleases": false,
  "encrypted": {
    "npmrc":
      ""
  }
}

Renovate now gives me the following error;

Action Required: Fix Renovate Configuration

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

File: renovate.json
Error type: The renovate configuration file contains some invalid settings
Message: Invalid configuration option: combinePatchMinorReleases

Once you have resolved this problem (in this onboarding branch), Renovate will return to providing you with a preview of your repository's configuration.

Based on the documentation I could see these options have the potential to conflict.

• combinePatchMinorReleases: "Combine any patch and minor upgrades together into same branch/PR"
  -separatePatchReleases : "Separate patch and minor releases of dependencies into separate PRs"

Whats the best way to resolve this? Ideally, I think I'd like all the patch/minor updates in one PR and then majors one per dependency. This is probably less ideal long term but initially we're going to have a lot of PRs to process otherwise.

Hey, the bot created an issue with our Renovate config, but this had been working and I'm not sure what the issue is with the config unless something has changed here recently that means it's no longer valid.

This is our Renovate config:

{
  "extends": [":library"],
  "automerge": true,
  "automergeType": "branch-push",
  "major": {
    "automerge": false
  }
}

Here is custom preset used
https://github.com/nuxt/renovate-config-nuxt

Here is grouped PR nuxt/nuxt#3986
And here is patch releases each was opened with a separate PR
nuxt/nuxt#3979
nuxt/nuxt#3981
nuxt/nuxt#3977
etc
According to docs

Group all minor and patch updates together

They all should be in one PR, not a separate PR for each patch release

Microsoft is using a variety of Docker images on which .NET Core & ASP.NET Core applications depend, such as mcr.microsoft.com/dotnet/core/sdk & mcr.microsoft.com/dotnet/core/aspnet.

For Promitor I depend on those and receive update PRs, but they are seperated (example: tomkerkhove/promitor#831 & tomkerkhove/promitor#832) which is not ideal so I'd like to group them so that the CI works.

I'm looking to open a PR for adding this and was wondering if monorepo Docker images should also end up in https://github.com/renovatebot/presets/blob/master/packages/renovate-config-monorepo or if there are better ways to do this?

It’s too confusing with the config-help one. I suggest calling it “presets”.