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
Jul 20, 2019
Merged

Configure Renovate #1

merged 1 commit into from
Jul 20, 2019

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 28, 2019

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

🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.


Detected Package Files

  • package.json (npm)

Configuration Summary

Based on the default config's presets, Renovate will:

  • Start dependency updates only once this Configure Renovate PR is merged
  • 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, vendor 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 open PRs at any time
  • Group known monorepo packages together
  • Use curated list of recommended non-monorepo package groupings

🔡 Would you like to change the way Renovate is upgrading your dependencies? Simply edit the renovate.json in this branch with your custom config and the list of Pull Requests in the "What to Expect" section below will be updated the next time Renovate runs.


What to Expect

With your current configuration, Renovate will create 1 Pull Request:

Update dependency through2 to v3
  • Schedule: "at any time"
  • Branch name: renovate/through2-3.x
  • Upgrade through2 to ^3.0.0

❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section.
If you need any further assistance then you can also request help here.


This PR has been generated by Renovate Bot. View repository job log here.

@renovate renovate bot force-pushed the renovate/configure branch 2 times, most recently from 1e3a584 to feda408 Compare May 19, 2019 09:53
@renovate renovate bot force-pushed the renovate/configure branch 2 times, most recently from 5b48e8a to b74a528 Compare May 25, 2019 17:53
@renovate renovate bot force-pushed the renovate/configure branch 7 times, most recently from 86daf82 to 9a33834 Compare July 19, 2019 01:54
@zce zce merged commit 76e8eab into master Jul 20, 2019
@zce zce deleted the renovate/configure branch July 20, 2019 11:02
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.

2 participants