Skip to content
This repository has been archived by the owner on Jun 22, 2022. It is now read-only.

Configure Renovate #4

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Configure Renovate #4

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Oct 7, 2018

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.


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
  • Weekly schedule on early monday mornings
  • Disable pinning of docker dependency digests
  • Separate patch and minor releases of dependencies into separate PRs
  • Use semantic prefixes for commit messages and PR titles
  • Rebase existing PRs any time the base branch has been updated
  • Preserve (but continue to upgrade) any existing semver ranges
  • Run Renovate on following schedule: before 3am on Monday

🔡 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

It looks like your repository dependencies are already up-to-date and no Pull Requests will be necessary right away.


❓ 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 5 times, most recently from 2cde954 to e2a507e Compare November 6, 2018 01:41
@renovate renovate bot force-pushed the renovate/configure branch 8 times, most recently from fc8b262 to c2049d6 Compare November 14, 2018 01:50
@renovate renovate bot force-pushed the renovate/configure branch 8 times, most recently from 7aa155d to 1d780a8 Compare November 22, 2018 01:41
@renovate renovate bot force-pushed the renovate/configure branch 8 times, most recently from ebdaad5 to 006d363 Compare November 29, 2018 02:52
@renovate renovate bot force-pushed the renovate/configure branch from 006d363 to 553ece8 Compare November 30, 2018 03:57
@renovate renovate bot force-pushed the renovate/configure branch 7 times, most recently from 337fb4d to a84043a Compare January 11, 2019 00:25
@renovate renovate bot force-pushed the renovate/configure branch 4 times, most recently from ea97db1 to df3dbb6 Compare January 18, 2019 06:58
@renovate renovate bot force-pushed the renovate/configure branch 5 times, most recently from 51c938d to 4a2058e Compare January 26, 2019 06:59
@renovate renovate bot force-pushed the renovate/configure branch 4 times, most recently from fc8481d to b46f8bc Compare February 3, 2019 00:45
@renovate renovate bot force-pushed the renovate/configure branch 7 times, most recently from a1176fd to bdd15e0 Compare February 10, 2019 00:51
@renovate renovate bot force-pushed the renovate/configure branch from bdd15e0 to 4a369b1 Compare February 11, 2019 01:54
@renovate renovate bot force-pushed the renovate/configure branch from 4a369b1 to 3a4919f Compare February 12, 2019 02:58
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant