Skip to content

Configure Renovate#31

Merged
ryasmi merged 2 commits intomasterfrom
renovate/configure
Oct 25, 2017
Merged

Configure Renovate#31
ryasmi merged 2 commits intomasterfrom
renovate/configure

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Oct 6, 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 Getting Started Configuring Renovate 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 fix(deps): for dependencies and chore(deps): for all others
  • Keep existing branches updated even when not scheduled
  • Disable automerging feature - wait for humans to merge all PRs
  • Keep package.json npm dependencies updated
  • Update existing lock files only when package.json is modified
  • Upgrade versions up to the "latest" tag in npm registry
  • Create branches/PRs for dependency upgrades as soon as they're available
  • Pin dependency versions for devDependencies and retain semver ranges for others

With your current configuration, renovate will initially create the following Pull Requests:

Pull Requests (2)
chore(deps): pin devdependencies
  • Branch name: renovate/pin-dependencies
  • Pins typescript in devDependencies to 2.5.3
  • Pins tslint in devDependencies to 5.8.0
  • Pins semantic-release in devDependencies to 8.2.2
  • Pins rimraf in devDependencies to 2.6.2
  • Pins nyc in devDependencies to 11.3.0
  • Pins mocha in devDependencies to 3.5.3
  • Pins lodash in devDependencies to 4.17.4
  • Pins jscpd in devDependencies to 0.6.15
  • Pins cz-conventional-changelog in devDependencies to 2.0.0
  • Pins commitizen in devDependencies to 2.9.6
  • Pins assert in devDependencies to 1.4.1
  • Pins @​types/node in devDependencies to 8.0.47
  • Pins @​types/mocha in devDependencies to 2.2.43
  • Pins @​types/lodash in devDependencies to 4.14.79
chore(deps): update dependency mocha to v4
  • Branch name: renovate/mocha-4.x
  • Upgrades mocha in devDependencies from ^3.4.0 to 4.0.1

Sometimes you may see multiple options for the same dependency (e.g. pinning in one branch and upgrading in another). This is expected and allows you the flexibility to choose which to merge first. Once you merge any PR, others will be updated or removed the next time Renovate runs.

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.

Our Configuration Docs should be helpful if you wish to modify any behaviour.


Don't want a renovate.json file?

You are not required to merge this Pull Request - Renovate will begin even if this "Configure Renovate" PR is closed unmerged and without a renovate.json file. However, it's recommended that you add configuration 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. If you make these configuration changes in this branch then the results will be described in this PR after the next time Renovate runs.

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 2 times, most recently from 69b8124 to 549010d Compare October 11, 2017 11:31
@renovate renovate Bot force-pushed the renovate/configure branch from 549010d to c298c38 Compare October 11, 2017 18:27
@ryasmi ryasmi self-requested a review October 25, 2017 12:58
@ryasmi ryasmi added the ci label Oct 25, 2017
@ryasmi ryasmi merged commit c1f7f08 into master Oct 25, 2017
@ryasmi ryasmi deleted the renovate/configure branch October 25, 2017 13:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant