Skip to content

Configure Renovate #1

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

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

Configure Renovate #1

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Feb 2, 2018

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 24 Pull Requests:

  1. chore(deps): pin dependencies
  1. chore(deps): update dependency @​types/jasmine to v2.8.6
  • Branch name: renovate/jasmine-2.x
  • Upgrades @types/jasmine in devDependencies from 2.5.38 to 2.8.6
  1. chore(deps): update dependency @​types/node to v6.0.101
  • Branch name: renovate/node-6.x
  • Upgrades @types/node in devDependencies from ~6.0.60 to 6.0.101
  1. chore(deps): update dependency codelyzer to v2.1.1
  • Branch name: renovate/codelyzer-2.x
  • Upgrades codelyzer in devDependencies from ~2.0.0 to 2.1.1
  1. chore(deps): update dependency jasmine-core to v2.99.1
  • Branch name: renovate/jasmine-core-2.x
  • Upgrades jasmine-core in devDependencies from ~2.5.2 to 2.99.1
  1. chore(deps): update dependency jasmine-spec-reporter to v3.3.0
  • Branch name: renovate/jasmine-spec-reporter-3.x
  • Upgrades jasmine-spec-reporter in devDependencies from ~3.2.0 to 3.3.0
  1. chore(deps): update dependency karma to v1.7.1
  • Branch name: renovate/karma-1.x
  • Upgrades karma in devDependencies from ~1.4.1 to 1.7.1
  1. chore(deps): update dependency karma-chrome-launcher to v2.2.0
  • Branch name: renovate/karma-chrome-launcher-2.x
  • Upgrades karma-chrome-launcher in devDependencies from ~2.0.0 to 2.2.0
  1. chore(deps): update dependency karma-coverage-istanbul-reporter to v0.3.1
  1. chore(deps): update dependency karma-jasmine to v1.1.1
  • Branch name: renovate/karma-jasmine-1.x
  • Upgrades karma-jasmine in devDependencies from ~1.1.0 to 1.1.1
  1. chore(deps): update dependency protractor to v5.3.0
  • Branch name: renovate/protractor-5.x
  • Upgrades protractor in devDependencies from ~5.1.0 to 5.3.0
  1. chore(deps): update dependency ts-node to v2.1.2
  • Branch name: renovate/ts-node-2.x
  • Upgrades ts-node in devDependencies from ~2.0.0 to 2.1.2
  1. chore(deps): update dependency tslint to v4.5.1
  • Branch name: renovate/tslint-4.x
  • Upgrades tslint in devDependencies from ~4.4.2 to 4.5.1
  1. chore(deps): update dependency typescript to v2.7.2
  • Branch name: renovate/typescript-2.x
  • Upgrades typescript in devDependencies from ~2.1.0 to 2.7.2
  1. fix(deps): update dependency core-js to v2.5.3
  • Branch name: renovate/core-js-2.x
  • Upgrades core-js in dependencies from ^2.4.1 to 2.5.3
  1. fix(deps): update dependency rxjs to v5.5.6
  • Branch name: renovate/rxjs-5.x
  • Upgrades rxjs in dependencies from ^5.1.0 to 5.5.6
  1. fix(deps): update dependency zone.js to v0.8.20
  • Branch name: renovate/zone.js-0.x
  • Upgrades zone.js in dependencies from ^0.7.6 to 0.8.20
  1. chore(deps): update angular monorepo packages
  1. chore(deps): update dependency codelyzer to v4
  • Branch name: renovate/codelyzer-4.x
  • Upgrades codelyzer in devDependencies from ~2.0.0 to 4.1.0
  1. chore(deps): update dependency jasmine-spec-reporter to v4
  • Branch name: renovate/jasmine-spec-reporter-4.x
  • Upgrades jasmine-spec-reporter in devDependencies from ~3.2.0 to 4.2.1
  1. chore(deps): update dependency karma to v2
  • Branch name: renovate/karma-2.x
  • Upgrades karma in devDependencies from ~1.4.1 to 2.0.0
  1. chore(deps): update dependency karma-coverage-istanbul-reporter to v1
  1. chore(deps): update dependency ts-node to v4
  • Branch name: renovate/ts-node-4.x
  • Upgrades ts-node in devDependencies from ~2.0.0 to 4.1.0
  1. chore(deps): update dependency tslint to v5
  • Branch name: renovate/tslint-5.x
  • Upgrades tslint in devDependencies from ~4.4.2 to 5.9.1

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