Skip to content


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time


This repository holds a Renovate shareable configuration, much like algolia/eslint-config-algolia.

Renovate keeps npm dependencies up-to-date the right way, the right features and right time.

How to use it

1. Create a renovate.json file:

If you have a JavaScript application (dashboard, static website generator), put this in your renovate.json:

  "extends": ["config:js-app", "github>algolia/renovate-config-algolia"]

If you have a JavaScript library:

  "extends": ["config:js-lib", "github>algolia/renovate-config-algolia"]

The only difference between the two configurations is that an application will have its devDependencies and dependencies pinned. While a JavaScript library will only have its devDependencies pinned. Read the Renovate docs, dependency pinning to learn more.

You do not need to install renovate-config-algolia, as it's automatically picked up by Renovate.

2. Activate Renovate

Go to, ask a GitHub admin of the organisation if you need help on how to do this step.

What's inside the configuration?

The Renovate configuration automerges any minor and patch updates to any dependencies in your repository. It will directly push to the GitHub default branch of your project.

It runs every weekend, Paris time.

We chose to have a configuration that directly merges PRs to avoid having a lot of Pull Requests to merge manually. If the update passes your test suite, then it's merged directly. If tests are not passing or if there's a major upgrade then the pull request will stay opened.