Skip to content

Configure Renovate #111

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

Merged
merged 1 commit into from
Nov 18, 2017
Merged

Configure Renovate #111

merged 1 commit into from
Nov 18, 2017

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 8, 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 fix(deps): for dependencies and chore(deps): 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 12 Pull Requests:

  1. chore(deps): pin devdependencies
  • Branch name: renovate/pin-dependencies
  • Pins yarn in devDependencies to 1.3.2
  • Pins xo in devDependencies to 0.18.2
  • Pins prettier in devDependencies to 1.8.2
  • Pins npx in devDependencies to 9.7.1
  • Pins lint-staged in devDependencies to 4.3.0
  • Pins lerna in devDependencies to 2.5.1
  • Pins husky in devDependencies to 0.14.3
  • Pins eslint-config-prettier in devDependencies to 2.7.0
  • Pins eslint in devDependencies to 4.11.0
  • Pins docsify-cli in devDependencies to 4.1.12
  • Pins @marionebl/sander in dependencies to 0.6.1
  • Pins xo in devDependencies to 0.18.2
  • Pins execa in dependencies to 0.7.0
  • Pins cross-env in devDependencies to 5.1.1
  • Pins concurrently in devDependencies to 3.5.0
  • Pins babel-register in devDependencies to 6.26.0
  • Pins babel-cli in devDependencies to 6.26.0
  • Pins pkg-dir in dependencies to 2.0.0
  • Pins execa in dependencies to 0.8.0
  • Pins @marionebl/sander in dependencies to 0.6.1
  • Pins babel-core in devDependencies to 6.26.0
  • Pins ava in devDependencies to 0.22.0
  • Pins throat in devDependencies to 4.1.0
  • Pins cross-env in devDependencies to 5.1.1
  • Pins concurrently in devDependencies to 3.5.0
  • Pins commitizen in devDependencies to 2.9.6
  • Pins babel-register in devDependencies to 6.26.0
  • Pins babel-cli in devDependencies to 6.26.0
  • Pins ava in devDependencies to 0.20.0
  • Pins meow in dependencies to 3.7.0
  • Pins execa in dependencies to 0.7.0
  • Pins cross-env in devDependencies to 5.1.1
  • Pins concurrently in devDependencies to 3.5.0
  • Pins babel-register in devDependencies to 6.26.0
  • Pins babel-cli in devDependencies to 6.26.0
  • Pins ava in devDependencies to 0.22.0
  • Pins lodash in dependencies to 4.17.4
  • Pins globby in dependencies to 4.1.0
  • Pins ava in devDependencies to 0.22.0
  • Pins lerna in dependencies to 2.5.1
  • Pins import-from in dependencies to 2.1.0
  • Pins xo in devDependencies to 0.18.2
  • Pins string-to-stream in devDependencies to 1.1.0
  • Pins sander in devDependencies to 0.6.0
  • Pins rimraf in devDependencies to 2.6.2
  • Pins resolve-bin in devDependencies to 0.4.0
  • Pins mkdirp in devDependencies to 0.5.1
  • Pins execa in devDependencies to 0.7.0
  • Pins dependency-check in devDependencies to 2.9.1
  • Pins cross-env in devDependencies to 5.1.1
  • Pins concurrently in devDependencies to 3.5.0
  • Pins babel-register in devDependencies to 6.26.0
  • Pins babel-cli in devDependencies to 6.26.0
  • Pins ava in devDependencies to 0.18.2
  • Pins meow in dependencies to 3.7.0
  • Pins lodash in dependencies to 4.17.4
  • Pins get-stdin in dependencies to 5.0.1
  • Pins chalk in dependencies to 2.3.0
  • Pins babel-polyfill in dependencies to 6.26.0
  • Pins resolve-pkg in dependencies to 1.0.0
  • Pins read-pkg in dependencies to 2.0.0
  1. fix(deps): update dependency read-pkg to v3
  • Branch name: renovate/read-pkg-3.x
  • Upgrades read-pkg in dependencies from ^2.0.0 to 3.0.0
  1. chore(deps): update dependency ava to v0.23.0
  • Branch name: renovate/ava-0.x
  • Upgrades ava in devDependencies from 0.22.0 to 0.23.0
  • Upgrades ava in devDependencies from ^0.22.0 to 0.23.0
  • Upgrades ava in devDependencies from ^0.20.0 to 0.23.0
  • Upgrades ava in devDependencies from ^0.22.0 to 0.23.0
  • Upgrades ava in devDependencies from ^0.22.0 to 0.23.0
  • Upgrades ava in devDependencies from ^0.18.2 to 0.23.0
  1. fix(deps): update dependency execa to v0.8.0
  • Branch name: renovate/execa-0.x
  • Upgrades execa in dependencies from ^0.7.0 to 0.8.0
  • Upgrades execa in dependencies from ^0.7.0 to 0.8.0
  • Upgrades execa in devDependencies from 0.6.3 to 0.8.0
  • Upgrades execa in devDependencies from ^0.7.0 to 0.8.0
  1. chore(deps): update dependency lerna to v2.5.1
  • Branch name: renovate/lerna-2.x
  • Upgrades lerna in devDependencies from 2.4.0 to 2.5.1
  • Upgrades lerna in devDependencies from 2.0.0 to 2.5.1
  • Upgrades lerna in devDependencies from 2.4.0 to 2.5.1
  • Upgrades lerna in devDependencies from 2.0.0 to 2.5.1
  • Upgrades lerna in devDependencies from 2.0.0 to 2.5.1
  • Upgrades lerna in devDependencies from 2.0.0 to 2.5.1
  1. chore(deps): update dependency globby to v7
  • Branch name: renovate/globby-7.x
  • Upgrades globby in devDependencies from 6.1.0 to 7.0.0
  • Upgrades globby in dependencies from ^4.0.0 to 7.0.0
  1. chore(deps): update dependency resolve-from to v4
  • Branch name: renovate/resolve-from-4.x
  • Upgrades resolve-from in devDependencies from 3.0.0 to 4.0.0
  • Upgrades resolve-from in dependencies from ^3.0.0 to ^4.0.0
  1. chore(deps): update dependency dependency-check to v2.9.1
  • Branch name: renovate/dependency-check-2.x
  • Upgrades dependency-check in devDependencies from 2.7.0 to 2.9.1
  1. chore(deps): update dependency nyc to v11
  • Branch name: renovate/nyc-11.x
  • Upgrades nyc in devDependencies from 10.3.2 to 11.3.0
  1. chore(deps): update dependency rimraf to v2.6.2
  • Branch name: renovate/rimraf-2.x
  • Upgrades rimraf in devDependencies from 2.6.1 to 2.6.2
  • Upgrades rimraf in devDependencies from 2.6.1 to 2.6.2
  1. fix(deps): update dependency chalk to ^2.0.0
  • Branch name: renovate/chalk-2.x
  • Upgrades chalk in dependencies from ^1.1.1 to ^2.0.0
  1. chore(deps): update dependency lint-staged to v5
  • Branch name: renovate/lint-staged-5.x
  • Upgrades lint-staged in devDependencies from ^4.0.1 to 5.0.0

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 16 times, most recently from 61bc2c7 to 6b20c68 Compare November 17, 2017 10:03
@renovate renovate bot force-pushed the renovate/configure branch from 6b20c68 to d703016 Compare November 18, 2017 10:02
@marionebl marionebl merged commit e755726 into master Nov 18, 2017
@marionebl marionebl deleted the renovate/configure branch November 18, 2017 12:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant