Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configure Renovate #36

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Configure Renovate #36

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Aug 25, 2017

Welcome to Renovate!

This is an onboarding PR to help you understand and configure Renovate before any regular Pull Requests begin. Once you close this Pull Request, Renovate will begin keeping your dependencies up-to-date via automated Pull Requests.

If you have any questions, try reading our Configuring Renovate help 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 PR is merged or closed
  • Separate major versions of dependencies into individual branches/PRs
  • Combine any patch and minor upgrades together into same branch/PR
  • Upgrade to unstable versions only if the existing version is unstable
  • Raise PRs immediately (after branch is created)
  • Use renovate/ as prefix for all branch names
  • If semantic commits detected, use semantic commit type fix for dependencies and chore for all others
  • Keep existing branches updated even when not scheduled
  • Disable automerging feature - wait for humans to merge all PRs
  • 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 leading digit indicates unstable

Would you like to change the way Renovate is upgrading your dependencies? Simply edit the renovate.json in this branch and this Pull Request description will be updated the next time Renovate runs.


What to Expect

With your current configuration, Renovate will create 9 Pull Requests:

  1. chore(deps): pin dependencies
  1. chore(deps): update dependency babel-eslint to v8
  • Branch name: renovate/babel-eslint-8.x
  • Upgrades babel-eslint in devDependencies from ^4.1.6 to 8.0.3
  1. chore(deps): update dependency babel-loader to v7
  • Branch name: renovate/babel-loader-7.x
  • Upgrades babel-loader in devDependencies from ^6.2.1 to 7.1.2
  1. chore(deps): update dependency babel-plugin-add-module-exports to v0.2.1
  1. chore(deps): update dependency eslint to v4
  • Branch name: renovate/eslint-4.x
  • Upgrades eslint in devDependencies from ^1.10.3 to 4.12.1
  1. chore(deps): update dependency eslint-config-airbnb to v16
  • Branch name: renovate/eslint-config-airbnb-16.x
  • Upgrades eslint-config-airbnb in devDependencies from ^4.0.0 to 16.1.0
  1. chore(deps): update dependency eslint-plugin-import to v2
  • Branch name: renovate/eslint-plugin-import-2.x
  • Upgrades eslint-plugin-import in devDependencies from ^0.13.0 to 2.8.0
  1. chore(deps): update dependency lodash to v4
  • Branch name: renovate/lodash-monorepo
  • Upgrades lodash in devDependencies from ^3.10.1 to 4.17.4
  1. chore(deps): update dependency webpack to v3
  • Branch name: renovate/webpack-3.x
  • Upgrades webpack in devDependencies from ^1.12.9 to 3.9.1

Don't want a renovate.json file?

Renovate will begin once this "Configure Renovate" PR is merged or closed, but it's recommended that you add the renovate.json 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 PR.

Want to start over?

If you'd like Renovate to recreate this "Configure Renovate" PR from scratch - for example if your base branch has had substantial changes - then you need to:

  1. (IMPORTANT) Rename this PR to something else, e.g. "Configure Renovate - old"
  2. Close the PR and delete the branch

If later on you ever wish to reconfigure Renovate then you can use this same trick of renaming the PR, but you'll also need to delete any renovate.json file too. You should then get a new "Configure Renovate" PR like this.

@renovate renovate bot force-pushed the renovate/configure branch 3 times, most recently from cf2898d to f443e96 Compare October 11, 2017 18:48
@renovate renovate bot force-pushed the renovate/configure branch 12 times, most recently from 139be01 to 9bbb649 Compare November 16, 2017 09:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants