renovate-config-next

Shared Renovate configuration for FT.com.

Our Configuration

We have a custom set of rules for FT.com repositories. We are generally...

• Letting Renovate decide how to modify or update existing ranges on Financial Times owned dependencies

• Using semver ranges for all other dependencies (including n-ui), only opening pull requests for major version updates

• Grouping updates for the following monorepos into a single pull request

  • x-dash
  • Page Kit
  • Tool Kit
  • Reliability Kit
  • Ads
  • Privacy

• Upgrading Node.js to LTS versions, including any under their maintenance period.

• Tracking major updates of devDependencies and Origami components (o-* packages) in the Renovate master issue, but we're not opening pull requests automatically for them

• All external dependencies updates will be managed in the Dependency Dashboard

Read more about how we're using Renovate on its wiki page.

Usage

Reference the shared configuration in your repository's own renovate.json like so:

{
  "extends": [
    "github>financial-times/renovate-config-next"
  ]
}

Development

Our shared configuration is defined in renovate-config.json5. This file is transpiled on a pre-commit hook into the renovate.json file. Modifying the renovate.json won't allow you to commit, so make sure all of your modifications go on the json5 version. If for some reason there are untracked changes on your renovate.json file, make sure to delete the file to be able to commit.