Skip to content
This repository has been archived by the owner on Apr 27, 2021. It is now read-only.

Configure Renovate #155

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

Configure Renovate #155

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Dec 12, 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.


Detected Package Files

  • Dockerfile (dockerfile)
  • app/gage_client/dev-requirements.txt (pip_requirements)
  • app/gage_client/requirements.txt (pip_requirements)
  • app/requirements.txt (pip_requirements)

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

Update dependency Adafruit_BBIO to v1.1.1
  • Schedule: "at any time"
  • Branch name: renovate/adafruit_bbio-1.x
  • Upgrade Adafruit_BBIO to ==1.1.1
Update dependency PyYAML to v3.13
  • Schedule: "at any time"
  • Branch name: renovate/pyyaml-3.x
  • Upgrade PyYAML to ==3.13
Update dependency ipython to v5.8.0
  • Schedule: "at any time"
  • Branch name: renovate/ipython-5.x
  • Upgrade ipython to ==5.8.0
Update dependency mock to v1.3.0
  • Schedule: "at any time"
  • Branch name: renovate/mock-1.x
  • Upgrade mock to ==1.3.0
Update dependency nose to v1.3.7
  • Schedule: "at any time"
  • Branch name: renovate/nose-1.x
  • Upgrade nose to ==1.3.7
Update dependency nosexcover to v1.0.11
  • Schedule: "at any time"
  • Branch name: renovate/nosexcover-1.x
  • Upgrade nosexcover to ==1.0.11
Update dependency peewee to v2.10.2
  • Schedule: "at any time"
  • Branch name: renovate/peewee-2.x
  • Upgrade peewee to ==2.10.2
Update dependency pyserial to v3.4
  • Schedule: "at any time"
  • Branch name: renovate/pyserial-3.x
  • Upgrade pyserial to ==3.4
Update dependency python-coveralls to v2.9.2
  • Schedule: "at any time"
  • Branch name: renovate/python-coveralls-2.x
  • Upgrade python-coveralls to ==2.9.2
Update dependency python-networkmanager to v2.1
  • Schedule: "at any time"
  • Branch name: renovate/python-networkmanager-2.x
  • Upgrade python-networkmanager to ==2.1
Update dependency raven to v6.10.0
  • Schedule: "at any time"
  • Branch name: renovate/raven-6.x
  • Upgrade raven to ==6.10.0
Update dependency requests to v2.20.0 [SECURITY]
  • Branch name: renovate/pypi-requests-vulnerability
  • Upgrade requests to ==2.20.0
Update dependency responses to v0.10.6
  • Schedule: "at any time"
  • Branch name: renovate/responses-0.x
  • Upgrade responses to ==0.10.6
Update dependency sh to v1.12.14
  • Schedule: "at any time"
  • Branch name: renovate/sh-1.x
  • Upgrade sh to ==1.12.14
Update dependency six to v1.12.0
  • Schedule: "at any time"
  • Branch name: renovate/six-1.x
  • Upgrade six to ==1.12.0
Update dependency PyYAML to v5
  • Schedule: "at any time"
  • Branch name: renovate/pyyaml-5.x
  • Upgrade PyYAML to ==5.1.1
Update dependency coverage to v4
  • Schedule: "at any time"
  • Branch name: renovate/coverage-4.x
  • Upgrade coverage to ==4.5.3
Update dependency ipython to v7
  • Schedule: "at any time"
  • Branch name: renovate/ipython-7.x
  • Upgrade ipython to ==7.6.1
Update dependency itsdangerous to v1
  • Schedule: "at any time"
  • Branch name: renovate/itsdangerous-1.x
  • Upgrade itsdangerous to ==1.1.0
Update dependency mock to v3
  • Schedule: "at any time"
  • Branch name: renovate/mock-3.x
  • Upgrade mock to ==3.0.5
Update dependency peewee to v3
  • Schedule: "at any time"
  • Branch name: renovate/peewee-3.x
  • Upgrade peewee to ==3.9.6

🚸 Branch creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or spam the project. See docs for prhourlylimit for details.


❓ 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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant