Skip to content

Configure Renovate#4

Open
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/configure
Open

Configure Renovate#4
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/configure

Conversation

@renovate
Copy link

@renovate renovate bot commented Apr 9, 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

  • docker-compose.yaml (docker-compose)
  • Dockerfile (dockerfile)
  • 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 40 Pull Requests:

Update dependency Django to v1.11.20
  • Schedule: "at any time"
  • Branch name: renovate/django-1.x
  • Upgrade Django to ==1.11.20
Update dependency PyMySQL to v0.9.3
  • Schedule: "at any time"
  • Branch name: renovate/pymysql-0.x
  • Upgrade PyMySQL to ==0.9.3
Update dependency beautifulsoup4 to v4.7.1
  • Schedule: "at any time"
  • Branch name: renovate/beautifulsoup4-4.x
  • Upgrade beautifulsoup4 to ==4.7.1
Update dependency billiard to v3.6.0.0
  • Schedule: "at any time"
  • Branch name: renovate/billiard-3.x
  • Upgrade billiard to ==3.6.0.0
Update dependency boto to v2.49.0
  • Schedule: "at any time"
  • Branch name: renovate/boto-2.x
  • Upgrade boto to ==2.49.0
Update dependency celery to v3.1.26.post2
  • Schedule: "at any time"
  • Branch name: renovate/celery-3.x
  • Upgrade celery to ==3.1.26.post2
Update dependency decorator to v4.4.0
  • Schedule: "at any time"
  • Branch name: renovate/decorator-4.x
  • Upgrade decorator to ==4.4.0
Update dependency django-cors-headers to v1.3.1
  • Schedule: "at any time"
  • Branch name: renovate/django-cors-headers-1.x
  • Upgrade django-cors-headers to ==1.3.1
Update dependency djangorestframework to v3.9.2
  • Schedule: "at any time"
  • Branch name: renovate/djangorestframework-3.x
  • Upgrade djangorestframework to ==3.9.2
Update dependency elasticsearch to v2.4.1
  • Schedule: "at any time"
  • Branch name: renovate/elasticsearch-2.x
  • Upgrade elasticsearch to ==2.4.1
Update dependency jieba to v0.39
  • Schedule: "at any time"
  • Branch name: renovate/jieba-0.x
  • Upgrade jieba to ==0.39
Update dependency kombu to v3.0.37
  • Schedule: "at any time"
  • Branch name: renovate/kombu-3.x
  • Upgrade kombu to ==3.0.37
Update dependency lxml to v3.8.0
  • Schedule: "at any time"
  • Branch name: renovate/lxml-3.x
  • Upgrade lxml to ==3.8.0
Update dependency mysqlclient to v1.4.2.post1
  • Schedule: "at any time"
  • Branch name: renovate/mysqlclient-1.x
  • Upgrade mysqlclient to ==1.4.2.post1
Update dependency nltk to v3.4
  • Schedule: "at any time"
  • Branch name: renovate/nltk-3.x
  • Upgrade nltk to ==3.4
Update dependency numpy to v1.16.2
  • Schedule: "at any time"
  • Branch name: renovate/numpy-1.x
  • Upgrade numpy to ==1.16.2
Update dependency pyparsing to v2.4.0
  • Schedule: "at any time"
  • Branch name: renovate/pyparsing-2.x
  • Upgrade pyparsing to ==2.4.0
Update dependency python-dateutil to v2.8.0
  • Schedule: "at any time"
  • Branch name: renovate/python-dateutil-2.x
  • Upgrade python-dateutil to ==2.8.0
Update dependency pytz to v2016.10
  • Schedule: "at any time"
  • Branch name: renovate/pytz-2016.x
  • Upgrade pytz to ==2016.10
Update dependency redis to v2.10.6
  • Schedule: "at any time"
  • Branch name: renovate/redis-2.x
  • Upgrade redis to ==2.10.6
Update dependency requests to v2.21.0 [SECURITY]
  • Branch name: renovate/pip_requirements-requests-vulnerability
  • Upgrade requests to ==2.21.0
Update dependency shortuuid to v0.5.0
  • Schedule: "at any time"
  • Branch name: renovate/shortuuid-0.x
  • Upgrade shortuuid to ==0.5.0
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 textrank4zh to v0.3
  • Schedule: "at any time"
  • Branch name: renovate/textrank4zh-0.x
  • Upgrade textrank4zh to ==0.3
Update dependency url-normalize to v1.4.1
  • Schedule: "at any time"
  • Branch name: renovate/url-normalize-1.x
  • Upgrade url-normalize to ==1.4.1
Update dependency urllib3 to v1.24.1 [SECURITY]
  • Branch name: renovate/pip_requirements-urllib3-vulnerability
  • Upgrade urllib3 to ==1.24.1
Update dependency w3lib to v1.20.0
  • Schedule: "at any time"
  • Branch name: renovate/w3lib-1.x
  • Upgrade w3lib to ==1.20.0
Update python Docker tag to v3.7.3
  • Schedule: "at any time"
  • Branch name: renovate/docker-python-3.x
  • Upgrade python to 3.7.3
Update dependency Django to v2
  • Schedule: "at any time"
  • Branch name: renovate/django-2.x
  • Upgrade Django to ==2.2
Update dependency amqp to v2
  • Schedule: "at any time"
  • Branch name: renovate/amqp-2.x
  • Upgrade amqp to ==2.4.2
Update dependency celery to v4
  • Schedule: "at any time"
  • Branch name: renovate/celery-4.x
  • Upgrade celery to ==4.3.0
Update dependency cssselect to v1
  • Schedule: "at any time"
  • Branch name: renovate/cssselect-1.x
  • Upgrade cssselect to ==1.0.3
Update dependency django-cors-headers to v2
  • Schedule: "at any time"
  • Branch name: renovate/django-cors-headers-2.x
  • Upgrade django-cors-headers to ==2.5.2
Update dependency elasticsearch to v7
  • Schedule: "at any time"
  • Branch name: renovate/elasticsearch-7.x
  • Upgrade elasticsearch to ==7.0.0
Update dependency jsonfield to v2
  • Schedule: "at any time"
  • Branch name: renovate/jsonfield-2.x
  • Upgrade jsonfield to ==2.0.2
Update dependency kombu to v4
  • Schedule: "at any time"
  • Branch name: renovate/kombu-4.x
  • Upgrade kombu to ==4.5.0
Update dependency lxml to v4
  • Schedule: "at any time"
  • Branch name: renovate/lxml-4.x
  • Upgrade lxml to ==4.3.3
Update dependency networkx to v2
  • Schedule: "at any time"
  • Branch name: renovate/networkx-2.x
  • Upgrade networkx to ==2.3
Update dependency pytz to v2019
  • Schedule: "at any time"
  • Branch name: renovate/pytz-2019.x
  • Upgrade pytz to ==2019.1
Update dependency redis to v3
  • Schedule: "at any time"
  • Branch name: renovate/redis-3.x
  • Upgrade redis to ==3.2.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 Renovate Bot. View repository job log here.

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.

1 participant