Configure Renovate
Welcome to Renovate!
This is an onboarding MR to help you understand and configure Renovate before any regular Merge Requests begin. Once you close this Merge Request, Renovate will begin keeping your dependencies up-to-date via automated Merge Requests.
If you have any questions, try reading our Getting Started Configuring Renovate page first, or feel free to ask the app author @rarkins a question in a comment below.
Configuration Summary
Based on the currently configured presets, Renovate will:
- Start dependency updates once this Configure Renovate MR is merged or closed
- Separate major versions of dependencies into individual branches/MRs
- Combine any patch and minor upgrades together into same branch/MR
- Upgrade to unstable versions only if the existing version is unstable
- Raise MRs immediately (after branch is created)
- Use
renovate/
as prefix for all branch names - If semantic commits detected, use semantic commit type
fix
for dependencies andchore
for all others - Keep existing branches updated even when not scheduled
- Disable automerging feature - wait for humans to merge all MRs
- Update existing lock files only when
package.json
is modified - Autodetect whether to pin dependencies or maintain ranges
- Odd version numbers are classified as unstable
- Preconfigure dependencies where an odd major version indicates unstable (Docker-only)
With your current configuration, renovate will initially create the following Merge Requests:
Merge Requests (20) |
---|
chore(deps): update dependency eslint-plugin-prettier to v2.4.0
|
fix(deps): update dependency ini to v1.3.5
|
chore(deps): update dependency file-loader to v1.1.6
|
chore(deps): update dependency eslint-plugin-react to v7.5.1
|
chore(deps): update dependency babel-eslint to v8.0.3
|
chore(deps): update dependency babel-plugin-transform-react-remove-prop-types to v0.4.12
|
chore(deps): update dependency bootstrap-kresus to v0.0.5
|
chore(deps): update dependency copy-webpack-plugin to v4.3.0
|
chore(deps): update dependency dygraphs to v2.1.0
|
chore(deps): update dependency eslint to v4.13.1
|
fix(deps): update dependency moment to v2.20.0
|
fix(deps): update dependency nodemailer to v4.4.1
|
chore(deps): update dependency onchange to v3.3.0
|
fix(deps): update dependency pouchdb to v6.4.0
|
chore(deps): update dependency prettier to v1.9.2
|
chore(deps): update dependency react-datepicker to v0.64.0
|
chore(deps): renovate react monorepo packages |
chore(deps): update dependency style-loader to v0.19.1
|
chore(deps): update dependency webpack to v3.10.0
|
chore(deps): update dependency webpack-spritesmith to v0.3.6
|
Sometimes you may see multiple options for the same dependency (e.g. pinning in one branch and upgrading in another). This is expected and allows you the flexibility to choose which to merge first. Once you merge any MR, others will be updated or removed the next time Renovate runs.
Would you like to change the way Renovate is upgrading your dependencies? Simply edit the renovate.json
in this branch and this Merge Request description will be updated the next time Renovate runs.
Our Configuration Docs should be helpful if you wish to modify any behaviour.
renovate.json
file?
Don't want a You are not required to merge this Merge Request - Renovate will begin even if this "Configure Renovate" MR is closed unmerged and without a renovate.json
file. However, it's recommended that you add configuration to your repository to ensure behaviour matches what you see described here.
Alternatively, you can add the same configuration settings into a "renovate" section of your package.json
file(s) in this branch and delete the renovate.json
from this MR. If you make these configuration changes in this branch then the results will be described in this MR after the next time Renovate runs.
Want to start over?
If you'd like Renovate to recreate this "Configure Renovate" MR from scratch - for example if your base branch has had substantial changes - then you need to:
- (IMPORTANT) Rename this MR to something else, e.g. "Configure Renovate - old"
- Close the MR and delete the branch
If later on you ever wish to reconfigure Renovate then you can use this same trick of renaming the MR, but you'll also need to delete any renovate.json
file too. You should then get a new "Configure Renovate" MR like this.