Skip to content

Conversation

@renovate
Copy link

@renovate renovate bot commented Aug 25, 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 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

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

  1. Update dependency graphql-tag to ^2.0.0
  • Branch name: renovate/graphql-tag-2.x
  • Upgrades graphql-tag in dependencies from ^1.2.3 to ^2.0.0
  1. Update dependency highlight.js to v9.12.0
  • Branch name: renovate/highlight.js-9.x
  • Upgrades highlight.js in dependencies from 9.7.0 to 9.12.0
  1. Update dependency jsdoc-to-markdown to v3
  • Branch name: renovate/jsdoc-to-markdown-3.x
  • Upgrades jsdoc-to-markdown in dependencies from 2.0.1 to 3.0.2
  1. Update dependency lodash to v4.17.4
  • Branch name: renovate/lodash-monorepo
  • Upgrades lodash in dependencies from 4.16.4 to 4.17.4
  1. Update dependency marked to v0.3.7
  • Branch name: renovate/marked-0.x
  • Upgrades marked in dependencies from 0.3.6 to 0.3.7
  1. Renovate angular monorepo packages
  1. Update dependency @​types/body-parser to v0.0.34
  • Branch name: renovate/types-body-parser-0.x
  • Upgrades @​types/body-parser in devDependencies from 0.0.29 to 0.0.34
  1. Update dependency @​types/body-parser to v1
  • Branch name: renovate/types-body-parser-1.x
  • Upgrades @​types/body-parser in devDependencies from 0.0.29 to 1.16.8
  1. Update dependency @​types/compression to v0.0.35
  • Branch name: renovate/types-compression-0.x
  • Upgrades @​types/compression in devDependencies from 0.0.29 to 0.0.35
  1. Pin Dependencies
  • Branch name: renovate/pin-dependencies
  • Pins typescript in devDependencies to 2.6.2
  • Pins striptags in devDependencies to 2.2.1
  • Pins moment in devDependencies to 2.19.3
  • Pins @​types/serve-static in devDependencies to 1.13.1
  • Pins @​types/node in devDependencies to 6.0.92
  • Pins @​types/lodash in devDependencies to 4.14.86
  • Pins @​types/highlight.js in devDependencies to 9.12.2
  • Pins @​types/hammerjs in devDependencies to 2.0.35
  • Pins @​types/express-serve-static-core in devDependencies to 4.0.57
  • Pins @​types/express in devDependencies to 4.0.39
  • Pins @​types/cookie-parser in devDependencies to 1.4.1
  1. Update dependency @​types/mime to v0.0.29
  • Branch name: renovate/types-mime-0.x
  • Upgrades @​types/mime in devDependencies from 0.0.28 to 0.0.29
  1. Update dependency @​types/mime to v2
  • Branch name: renovate/types-mime-2.x
  • Upgrades @​types/mime in devDependencies from 0.0.28 to 2.0.0
  1. Update dependency @​types/node to v8
  • Branch name: renovate/types-node-8.x
  • Upgrades @​types/node in devDependencies from ^6.0.38 to 8.0.53
  1. Update dependency autoprefixer to v6.7.7
  • Branch name: renovate/autoprefixer-6.x
  • Upgrades autoprefixer in devDependencies from 6.5.1 to 6.7.7
  1. Update dependency autoprefixer to v7
  • Branch name: renovate/autoprefixer-7.x
  • Upgrades autoprefixer in devDependencies from 6.5.1 to 7.1.6
  1. Update dependency parse5 to v2.2.3
  • Branch name: renovate/parse5-2.x
  • Upgrades parse5 in devDependencies from 2.2.1 to 2.2.3
  1. Update dependency parse5 to v3
  • Branch name: renovate/parse5-3.x
  • Upgrades parse5 in devDependencies from 2.2.1 to 3.0.3
  1. Update dependency preboot to v5
  • Branch name: renovate/preboot-5.x
  • Upgrades preboot in devDependencies from 4.5.2 to 5.1.7
  1. Update dependency request to v2.83.0
  • Branch name: renovate/request-2.x
  • Upgrades request in devDependencies from 2.76.0 to 2.83.0
  1. Update dependency rimraf to v2.6.2
  • Branch name: renovate/rimraf-2.x
  • Upgrades rimraf in devDependencies from 2.5.4 to 2.6.2
  1. Update dependency rxjs to v5.5.3
  • Branch name: renovate/rxjs-5.x
  • Upgrades rxjs in devDependencies from 5.0.0-beta.12 to 5.5.3
  1. Update dependency striptags to v3
  • Branch name: renovate/striptags-3.x
  • Upgrades striptags in devDependencies from ^2.1.1 to 3.1.1
  1. Update dependency zone.js to v0.8.18
  • Branch name: renovate/zone.js-0.x
  • Upgrades zone.js in devDependencies from 0.6.26 to 0.8.18

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 3 times, most recently from 43db452 to a64d335 Compare October 11, 2017 18:55
@renovate renovate bot force-pushed the renovate/configure branch from a64d335 to f6037a4 Compare November 10, 2017 16:09
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