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
Pin dependency versions for devDependencies and retain semver ranges for others
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.
Warnings (1)
Please correct - or verify that you can safely ignore - these warnings before you merge this PR.
angular2-meteor-accounts-ui: Dependency uses tag "../" as its version so that will never be changed by Renovate
What to Expect
With your current configuration, Renovate will create 17 Pull Requests:
chore(deps): renovate angular monorepo packages
Branch name: renovate/angular-monorepo
Upgrades @angular/router in devDependencies from ^3.0.0 to 5.0.5
Upgrades @angular/forms in devDependencies from ^2.0.0 to 5.0.5
Upgrades @angular/core in devDependencies from ^2.0.0 to 5.0.5
Upgrades @angular/common in devDependencies from ^2.0.0 to 5.0.5
Upgrades @angular/router in dependencies from 3.1.1 to 5.0.5
Upgrades @types/chai in devDependencies from ^3.4.33 to 4.0.6
chore(deps): update dependency chai to v4
Branch name: renovate/chai-4.x
Upgrades chai in devDependencies from 3.5.0 to 4.1.2
chore(deps): update dependency @types/node to v8
Branch name: renovate/types-node-8.x
Upgrades @types/node in devDependencies from ^6.0.39 to 8.0.53
chore(deps): update dependency @types/zone.js to v0.5.12
Branch name: renovate/types-zone.js-0.x
Upgrades @types/zone.js in devDependencies from 0.0.27 to 0.5.12
chore(deps): update dependency tslint to v5
Branch name: renovate/tslint-5.x
Upgrades tslint in devDependencies from ^3.6.0 to 5.8.0
chore(deps): update dependency typescript to v2.6.2
Branch name: renovate/typescript-2.x
Upgrades typescript in devDependencies from 2.0.0 to 2.6.2
chore(deps): update dependency typings to v2
Branch name: renovate/typings-2.x
Upgrades typings in devDependencies from ^1.3.0 to 2.1.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:
(IMPORTANT) Rename this PR to something else, e.g. "Configure Renovate - old"
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.
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:
renovate/
as prefix for all branch namesfix
for dependencies andchore
for all otherspackage.json
is modifieddevDependencies
and retain semver ranges for othersWould 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.Warnings (1)
Please correct - or verify that you can safely ignore - these warnings before you merge this PR.
angular2-meteor-accounts-ui
: Dependency uses tag "../
" as its version so that will never be changed by RenovateWhat to Expect
With your current configuration, Renovate will create 17 Pull Requests:
chore(deps): renovate angular monorepo packages
renovate/angular-monorepo
devDependencies
from^3.0.0
to5.0.5
devDependencies
from^2.0.0
to5.0.5
devDependencies
from^2.0.0
to5.0.5
devDependencies
from^2.0.0
to5.0.5
dependencies
from3.1.1
to5.0.5
dependencies
from2.1.1
to5.0.5
dependencies
from2.1.1
to5.0.5
dependencies
from2.1.1
to5.0.5
dependencies
from2.1.1
to5.0.5
dependencies
from2.1.1
to5.0.5
dependencies
from2.1.1
to5.0.5
fix(deps): update dependency angular2-meteor to v0.8.0
renovate/angular2-meteor-0.x
dependencies
from0.7.0
to0.8.0
chore(deps): update dependency angular2-meteor-polyfills to v0.2.0
renovate/angular2-meteor-polyfills-0.x
devDependencies
from^0.1.1
to0.2.0
dependencies
from0.1.1
to0.2.0
fix(deps): update dependency meteor-node-stubs to v0.3.2
renovate/meteor-node-stubs-0.x
dependencies
from0.2.3
to0.3.2
fix(deps): update dependency meteor-rxjs to v0.4.8
renovate/meteor-rxjs-0.x
dependencies
from0.4.0
to0.4.8
fix(deps): update dependency reflect-metadata to v0.1.10
renovate/reflect-metadata-0.x
dependencies
from0.1.8
to0.1.10
chore(deps): update dependency rxjs to v5.5.3
renovate/rxjs-5.x
devDependencies
from5.0.0-beta.12
to5.5.3
dependencies
from5.0.0-beta.12
to5.5.3
chore(deps): update dependency zone.js to v0.8.18
renovate/zone.js-0.x
devDependencies
from^0.6.23
to0.8.18
dependencies
from0.6.26
to0.8.18
fix(deps): update dependency meteor-typings to v1.4.1
renovate/meteor-typings-1.x
dependencies
from1.3.1
to1.4.1
chore(deps): pin dependencies
renovate/pin-dependencies
devDependencies
to0.6.26
devDependencies
to1.5.0
devDependencies
to3.15.1
devDependencies
to0.1.10
devDependencies
to1.4.1
devDependencies
to0.1.1
devDependencies
to1.8.5
devDependencies
to6.0.92
devDependencies
to2.2.44
devDependencies
to3.4.10
devDependencies
to2.4.10
devDependencies
to2.4.10
devDependencies
to2.4.10
devDependencies
to1.4.1
devDependencies
to2.2.44
devDependencies
to3.5.2
chore(deps): update dependency @types/chai to v4
renovate/types-chai-4.x
devDependencies
from^3.4.33
to4.0.6
chore(deps): update dependency chai to v4
renovate/chai-4.x
devDependencies
from3.5.0
to4.1.2
chore(deps): update dependency @types/node to v8
renovate/types-node-8.x
devDependencies
from^6.0.39
to8.0.53
chore(deps): update dependency @types/zone.js to v0.5.12
renovate/types-zone.js-0.x
devDependencies
from0.0.27
to0.5.12
chore(deps): update dependency tslint to v5
renovate/tslint-5.x
devDependencies
from^3.6.0
to5.8.0
chore(deps): update dependency typescript to v2.6.2
renovate/typescript-2.x
devDependencies
from2.0.0
to2.6.2
chore(deps): update dependency typings to v2
renovate/typings-2.x
devDependencies
from^1.3.0
to2.1.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 yourpackage.json
file(s) in this branch and delete therenovate.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:
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.