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 #18

Closed
wants to merge 1 commit into from
Closed

Configure Renovate #18

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Jul 27, 2017

Welcome to Renovate!

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

If you have any questions, try reading our Docs, particularly the Getting Started section. You can post questions in our Config Help repository or @ the app author @rarkins in this PR and he'll probably see it.


Detected Package Files

  • package.json

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
  • Ignore node_modules, bower_components, and various test/tests directories
  • Update existing lock files only when package.json is modified
  • Autodetect whether to pin dependencies or maintain ranges
  • Rate limit PR creation to a maximum of two per hour
  • Limit to maximum 20 concurrent Renovate PRs at any time

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. Try to use Config Presets (the extends array) when possible rather than raw config, as then this PR will be able to more accurately describe your settings.


What to Expect

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

  1. chore(deps): pin dependencies
  1. chore(deps): update dependency bel to v4.6.0
  • Branch name: renovate/bel-4.x
  • Upgrades bel in devDependencies from ^4.5.0 to 4.6.0
  1. chore(deps): update dependency commitizen to v2.9.6
  • Branch name: renovate/commitizen-2.x
  • Upgrades commitizen in devDependencies from ^2.8.6 to 2.9.6
  1. chore(deps): update dependency coveralls to v2.13.3
  • Branch name: renovate/coveralls-2.x
  • Upgrades coveralls in devDependencies from ^2.11.12 to 2.13.3
  1. chore(deps): update dependency koa to v1.6.0
  • Branch name: renovate/koa-1.x
  • Upgrades koa in devDependencies from ^1.2.4 to 1.6.0
  1. chore(deps): update dependency koa-better-body to v3.0.4
  • Branch name: renovate/koa-better-body-3.x
  • Upgrades koa-better-body in devDependencies from ^3.0.2 to 3.0.4
  1. chore(deps): update dependency mukla to v0.4.9
  • Branch name: renovate/mukla-0.x
  • Upgrades mukla in devDependencies from ^0.4.1 to 0.4.9
  1. chore(deps): update dependency bel to v5
  • Branch name: renovate/bel-5.x
  • Upgrades bel in devDependencies from ^4.5.0 to 5.1.7
  1. chore(deps): update dependency coveralls to v3
  • Branch name: renovate/coveralls-3.x
  • Upgrades coveralls in devDependencies from ^2.11.12 to 3.0.0
  1. chore(deps): update dependency cz-conventional-changelog to v2
  • Branch name: renovate/cz-conventional-changelog-2.x
  • Upgrades cz-conventional-changelog in devDependencies from ^1.2.0 to 2.1.0
  1. chore(deps): update dependency koa to v2
  • Branch name: renovate/koa-2.x
  • Upgrades koa in devDependencies from ^1.2.4 to 2.5.0
  1. chore(deps): update dependency nyc to v11
  • Branch name: renovate/nyc-11.x
  • Upgrades nyc in devDependencies from ^8.1.0 to 11.4.1
  1. chore(deps): update dependency standard to v11
  • Branch name: renovate/standard-11.x
  • Upgrades standard in devDependencies from ^8.0.0 to 11.0.0
  1. chore(deps): update dependency standard-version to v4
  • Branch name: renovate/standard-version-4.x
  • Upgrades standard-version in devDependencies from ^2.4.0 to 4.3.0
  1. chore(deps): update dependency supertest to v3
  • Branch name: renovate/supertest-3.x
  • Upgrades supertest in devDependencies from ^2.0.0 to 3.0.0
  1. fix(deps): update dependency extend-shallow to ^3.0.0
  • Branch name: renovate/extend-shallow-3.x
  • Upgrades extend-shallow in dependencies from ^2.0.1 to ^3.0.0
  1. fix(deps): update dependency koa-compose to ^4.0.0
  • Branch name: renovate/koa-compose-4.x
  • Upgrades koa-compose in dependencies from ^3.1.0 to ^4.0.0

@coveralls
Copy link

coveralls commented Jul 27, 2017

Coverage Status

Coverage remained the same at 100.0% when pulling 6cac12d on renovate/configure into e3e79fd on master.

@renovate renovate bot force-pushed the renovate/configure branch 4 times, most recently from 81e715d to 4813327 Compare August 5, 2017 04:16
@renovate renovate bot force-pushed the renovate/configure branch 3 times, most recently from 04d023c to 20c356b Compare August 18, 2017 12:11
@renovate renovate bot force-pushed the renovate/configure branch 3 times, most recently from b160a10 to d40eea4 Compare October 11, 2017 19:15
@renovate renovate bot force-pushed the renovate/configure branch 14 times, most recently from 1979b6a to e62a402 Compare November 16, 2017 10:01
@tunnckoCore tunnckoCore closed this Mar 7, 2018
@tunnckoCore tunnckoCore deleted the renovate/configure branch March 7, 2018 02:25
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.

None yet

2 participants