Skip to content
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

Configure Renovate #1

Merged
merged 1 commit into from
May 21, 2018
Merged

Configure Renovate #1

merged 1 commit into from
May 21, 2018

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 20, 2018

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

Renovate will begin keeping your dependencies up-to-date only once you merge this Pull Request.
If you close this Pull Request unmerged, then Renovate will be disabled.

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.


Detected Package Files

  • package.json (npm)

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
  • Do not separate patch and minor upgrades into separate PRs for the same dependency
  • 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
  • Ignore node_modules, bower_components, and various test/tests directories
  • Update existing lock files only when package.json is modified
  • Autodetect whether to pin dependencies or maintain ranges
  • Rate limit PR creation to a maximum of two per hour
  • Limit to maximum 20 concurrent Renovate PRs at any time

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

  1. chore(deps): pin dependencies
  1. chore(deps): update dependency danger to v3.7.11
  • Branch name: renovate/danger-3.x
  • Upgrades danger in devDependencies from ^3.7.4 to 3.7.11
  1. fix(deps): update dependency ink to ^0.5.0
  • Branch name: renovate/ink-0.x
  • Upgrades ink in dependencies from ^0.4.1 to ^0.5.0


This PR has been generated by Renovate Bot.

@evenchange4 evenchange4 merged commit 0e6507d into master May 21, 2018
@evenchange4 evenchange4 deleted the renovate/configure branch May 21, 2018 01:13
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.

None yet

2 participants