Configure Renovate

[renovate]

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

• requirements.txt (pip_requirements)

Configuration Summary

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

• Start dependency updates only once this onboarding 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)
• 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
• 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
• Ignore spring cloud 1.x releases
• Ignore http4s digest-based 1.x milestones
• Use node versioning for @types/node
• Limit concurrent requests to reduce load on Repology servers until we can fix this properly, see issue 10133

🔡 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 10 Pull Requests:

Update dependency Jinja2 to v2.10.1 [SECURITY]

• Branch name: renovate/pypi-Jinja2-vulnerability
• Merge into: master
• Upgrade Jinja2 to ==2.10.1

Update dependency SQLAlchemy to v1.3.0 [SECURITY]

• Branch name: renovate/pypi-SQLAlchemy-vulnerability
• Merge into: master
• Upgrade SQLAlchemy to ==1.3.0

Update dependency Flask to v0.12.5

• Schedule: ["at any time"]
• Branch name: renovate/flask-0.x
• Merge into: master
• Upgrade Flask to ==0.12.5

Update dependency DateTime to v4.3

• Schedule: ["at any time"]
• Branch name: renovate/datetime-4.x
• Merge into: master
• Upgrade DateTime to ==4.3

Update dependency Flask-SQLAlchemy to v2.5.1

• Schedule: ["at any time"]
• Branch name: renovate/flask-sqlalchemy-2.x
• Merge into: master
• Upgrade Flask-SQLAlchemy to ==2.5.1

Update dependency gunicorn to v19.10.0

• Schedule: ["at any time"]
• Branch name: renovate/gunicorn-19.x
• Merge into: master
• Upgrade gunicorn to ==19.10.0

Update dependency pytz to v2017.3

• Schedule: ["at any time"]
• Branch name: renovate/pytz-2017.x
• Merge into: master
• Upgrade pytz to ==2017.3

Update dependency Flask to v2

• Schedule: ["at any time"]
• Branch name: renovate/flask-2.x
• Merge into: master
• Upgrade Flask to ==2.0.1

Update dependency gunicorn to v20

• Schedule: ["at any time"]
• Branch name: renovate/gunicorn-20.x
• Merge into: master
• Upgrade gunicorn to ==20.1.0

Update dependency pytz to v2021

• Schedule: ["at any time"]
• Branch name: renovate/pytz-2021.x
• Merge into: master
• Upgrade pytz to ==2021.1

🚸 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 WhiteSource Renovate. View repository job log here.