Skip to content

Configure Renovate #62

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

Merged
merged 1 commit into from
Dec 29, 2017
Merged

Configure Renovate #62

merged 1 commit into from
Dec 29, 2017

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Dec 29, 2017

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.


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
  • Preconfigure dependencies where an odd major version indicates unstable (Docker-only)

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

  1. chore(deps): pin dependencies
  • Branch name: renovate/pin-dependencies
  • Pins tslint in devDependencies to 5.8.0
  • Pins ts-jest in devDependencies to 22.0.0
  • Pins mock-fs in devDependencies to 4.4.2
  • Pins jest in devDependencies to 22.0.4
  • Pins @​types/lodash in devDependencies to 4.14.91
  • Pins @​types/jest in devDependencies to 21.1.10
  • Pins serverless-plugin-typescript in devDependencies to 0.1.10
  • Pins @​types/lodash in devDependencies to 4.14.91
  1. chore(deps): update dependency serverless-plugin-typescript to v0.5.0
  1. chore(deps): update dependency serverless-plugin-typescript to v1
  1. fix(deps): update dependency globby to ^7.0.0
  • Branch name: renovate/globby-7.x
  • Upgrades globby in dependencies from ^6.1.0 to ^7.0.0
  1. chore(deps): update dependency @​types/fs-extra to v5
  • Branch name: renovate/types-fs-extra-5.x
  • Upgrades @​types/fs-extra in devDependencies from 4.0.7 to 5.0.0
  1. chore(deps): update dependency @​types/jest to v22
  • Branch name: renovate/types-jest-22.x
  • Upgrades @​types/jest in devDependencies from ^21.1.1 to 22.0.0

@schickling schickling merged commit d4ba1b4 into master Dec 29, 2017
@renovate renovate bot deleted the renovate/configure branch December 29, 2017 10:16
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.

1 participant