Configure Renovate

[renovate[bot]]

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

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

---

Detected Package Files

• 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, 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
• Group all packages published by Apollo GraphQL together
• Group all @polymer packages together

:abcd: 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 11 Pull Requests:

Update dependency SQLAlchemy to v1.2.12

- Schedule: "at any time" - Branch name: `renovate/sqlalchemy-1.x` - Upgrade SQLAlchemy to `==1.2.12`

Update dependency certifi to v2018.8.24

- Schedule: "at any time" - Branch name: `renovate/certifi-2018.x` - Upgrade certifi to `==2018.8.24`

Update dependency colorama to v0.4.0

- Schedule: "at any time" - Branch name: `renovate/colorama-0.x` - Upgrade [colorama](https://renovatebot.com/gh/tartley/colorama) to `==0.4.0`

Update dependency cryptography to v2.3.1

- Schedule: "at any time" - Branch name: `renovate/cryptography-2.x` - Upgrade [cryptography](https://renovatebot.com/gh/pyca/cryptography) to `==2.3.1`

Update dependency protobuf to v3.6.1

- Schedule: "at any time" - Branch name: `renovate/protobuf-3.x` - Upgrade protobuf to `==3.6.1`

Update dependency pycparser to v2.19

- Schedule: "at any time" - Branch name: `renovate/pycparser-2.x` - Upgrade [pycparser](https://renovatebot.com/gh/eliben/pycparser) to `==2.19`

Update dependency pylint to v1.9.3

- Schedule: "at any time" - Branch name: `renovate/pylint-1.x` - Upgrade [pylint](https://renovatebot.com/gh/PyCQA/pylint) to `==1.9.3`

Update dependency pytz to v2018.5

- Schedule: "at any time" - Branch name: `renovate/pytz-2018.x` - Upgrade pytz to `==2018.5`

Update dependency astroid to v2

- Schedule: "at any time" - Branch name: `renovate/astroid-2.x` - Upgrade [astroid](https://renovatebot.com/gh/PyCQA/astroid) to `==2.0.4`

Update dependency click to v7

- Schedule: "at any time" - Branch name: `renovate/click-7.x` - Upgrade click to `==7.0`

Update dependency pylint to v2

- Schedule: "at any time" - Branch name: `renovate/pylint-2.x` - Upgrade [pylint](https://renovatebot.com/gh/PyCQA/pylint) to `==2.1.1`

:children_crossing: Branch creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or spam the project. See: prHourlyLimit.

---

:question: If you have any questions, try reading the Docs, particularly the Getting Started section. Also, you can post questions about your config in Renovate's Config Help repository.

---

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

[renovate[bot]]

Renovate is disabled

Renovate is disabled due to lack of config. If you wish to reenable it, you can either (a) commit a config file to your base branch, or (b) rename this closed PR to trigger a replacement onboarding PR.