Configure Renovate

[renovate]

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
• Use version pinning (maintain a single version only and not semver ranges)

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

1. Renovate angular monorepo packages

• Branch name: renovate/angular-monorepo
• Upgrades @angular/router in dependencies from 3.1.2 to 5.0.5
• Upgrades @angular/platform-server in dependencies from 2.1.2 to 5.0.5
• Upgrades @angular/platform-browser-dynamic in dependencies from 2.1.2 to 5.0.5
• Upgrades @angular/platform-browser in dependencies from 2.1.2 to 5.0.5
• Upgrades @angular/http in dependencies from 2.1.2 to 5.0.5
• Upgrades @angular/material in dependencies from 2.0.0-alpha.9-3 to 5.0.0-rc.2
• Upgrades @angular/forms in dependencies from 2.1.2 to 5.0.5
• Upgrades @angular/core in dependencies from 2.1.2 to 5.0.5
• Upgrades @angular/compiler in dependencies from 2.1.2 to 5.0.5
• Upgrades @angular/common in dependencies from 2.1.2 to 5.0.5

2. Update dependency angular2-file-drop to v0.2.0

• Branch name: renovate/angular2-file-drop-0.x
• Upgrades angular2-file-drop in dependencies from 0.0.5 to 0.2.0

3. Pin Dependencies

• Branch name: renovate/pin-dependencies
• Pins @​types/mocha in devDependencies to 2.2.44
• Pins @​types/chai in devDependencies to 3.5.2
• Pins ionicons in dependencies to 3.0.0
• Pins angular2-meteor-polyfills in dependencies to 0.1.1
• Pins @​types/node in dependencies to 6.0.92

4. Update dependency @​types/node to v8

• Branch name: renovate/types-node-8.x
• Upgrades @​types/node in dependencies from ^6.0.45 to 8.0.53

5. Update dependency angular2-google-maps to v0.17.0

• Branch name: renovate/angular2-google-maps-0.x
• Upgrades angular2-google-maps in dependencies from 0.15.0 to 0.17.0

6. Update dependency angular2-meteor to v0.8.0

• Branch name: renovate/angular2-meteor-0.x
• Upgrades angular2-meteor in dependencies from 0.7.0 to 0.8.0

7. Update dependency angular2-meteor-polyfills to v0.2.0

• Branch name: renovate/angular2-meteor-polyfills-0.x
• Upgrades angular2-meteor-polyfills in dependencies from ^0.1.1 to 0.2.0

8. Update dependency ionic-angular to v2.3.0

• Branch name: renovate/ionic-angular-2.x
• Upgrades ionic-angular in dependencies from 2.0.0-rc.1 to 2.3.0

9. Update dependency ionic-angular to v3

• Branch name: renovate/ionic-angular-3.x
• Upgrades ionic-angular in dependencies from 2.0.0-rc.1 to 3.9.2

10. Update dependency meteor-node-stubs to v0.3.2

• Branch name: renovate/meteor-node-stubs-0.x
• Upgrades meteor-node-stubs in dependencies from 0.2.3 to 0.3.2

11. Update dependency meteor-rxjs to v0.4.8

• Branch name: renovate/meteor-rxjs-0.x
• Upgrades meteor-rxjs in dependencies from 0.4.3 to 0.4.8

12. Update dependency meteor-typings to v1.4.1

• Branch name: renovate/meteor-typings-1.x
• Upgrades meteor-typings in dependencies from 1.3.1 to 1.4.1

13. Update dependency ng2-pagination to v2

• Branch name: renovate/ng2-pagination-2.x
• Upgrades ng2-pagination in dependencies from 0.5.1 to 2.0.2

14. Update dependency reflect-metadata to v0.1.10

• Branch name: renovate/reflect-metadata-0.x
• Upgrades reflect-metadata in dependencies from 0.1.8 to 0.1.10

15. Update dependency rxjs to v5.5.3

• Branch name: renovate/rxjs-5.x
• Upgrades rxjs in dependencies from 5.0.0-beta.12 to 5.5.3

16. Update dependency zone.js to v0.8.18

• Branch name: renovate/zone.js-0.x
• Upgrades zone.js in dependencies from 0.6.26 to 0.8.18

17. Update dependency @​types/chai to v4

• Branch name: renovate/types-chai-4.x
• Upgrades @​types/chai in devDependencies from ^3.4.33 to 4.0.6

18. Update dependency chai to v4

• Branch name: renovate/chai-4.x
• Upgrades chai in devDependencies from 3.5.0 to 4.1.2

---

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.