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.

---

Configuration Summary

Based on the currently configured presets, Renovate will:

• Start dependency updates once this Configure Renovate MR is merged or closed
• Pin dependency versions for devDependencies and retain semver ranges for others
• Separate major versions of dependencies into individual branches/MRs
• Use the same branch/MR for both patch and minor upgrades of a dependency
• Only upgrade to stable npm versions
• Upgrade versions up to the "latest" tag in npm registry
• Create branches/MRs for dependency upgrades as soon as they're available
• Wait until branch tests have passed or failed before creating the MR
• Use renovate/ as prefix for all branch names
• If semantic commits detected, use fix(deps): for dependencies and chore(deps): for all others
• Disable automerging feature - wait for humans to merge all MRs
• Update existing lock files only when package.json is modified

---

With your current configuration, renovate will initially create the following Merge Requests:

Merge Requests (9)
fix(deps): update dependency express to v4.15.5 Branch name: renovate/express-4.x Upgrades express in dependencies from 4.15.4 to 4.15.5
fix(deps): update dependency nodemailer to v3 Branch name: renovate/nodemailer-3.x Upgrades nodemailer in dependencies from 2.7.2 to 3.1.8
fix(deps): update dependency nodemailer to v4 Branch name: renovate/nodemailer-4.x Upgrades nodemailer in dependencies from 2.7.2 to 4.1.1
chore(deps): update dependency eslint to v4 Branch name: renovate/eslint-4.x Upgrades eslint in devDependencies from 3.19.0 to 4.7.2
chore(deps): update dependency eslint-plugin-react to v7.4.0 Branch name: renovate/eslint-plugin-react-7.x Upgrades eslint-plugin-react in devDependencies from 7.3.0 to 7.4.0
chore(deps): update dependency prop-types to v15.6.0 Branch name: renovate/prop-types-15.x Upgrades prop-types in devDependencies from 15.5.10 to 15.6.0
chore(deps): update dependency react to v15.6.2 Branch name: renovate/react-15.x Upgrades react in devDependencies from 15.6.1 to 15.6.2
chore(deps): update dependency react-datepicker to v0.55.0 Branch name: renovate/react-datepicker-0.x Upgrades react-datepicker in devDependencies from 0.48.0 to 0.55.0
chore(deps): update dependency react-dom to v15.6.2 Branch name: renovate/react-dom-15.x Upgrades react-dom in devDependencies from 15.6.1 to 15.6.2

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.

---

Don't want a renovate.json file?

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.