dirigible-spreadsheet icon indicating copy to clipboard operation
dirigible-spreadsheet copied to clipboard

Configure Renovate

Open anaconda-renovate[bot] opened this issue 2 years ago • 0 comments

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)
  • renovate.json (renovate-config-presets)

Configuration Summary

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

  • Start dependency updates only once this onboarding PR is merged
  • Pin Docker digests.
  • Group known monorepo packages together.
  • Use curated list of recommended non-monorepo package groupings.
  • Convert pinned GitHub Action digests to SemVer.
  • Use node versioning for @types/node.
  • Use specific versioning for Red Hat-maintained container images.
  • Update _VERSION variables in Dockerfiles.
  • Update _VERSION environment variables in GitHub Action files.
  • Use the Anaconda Best Practice configuration from anaconda/renovate-config
  • Create a Dependency Dashboard as Issue, listing all upgrades
  • Open new PRs automatically every weekday before 6am UTC. You can manually trigger PRs from the Dependency Dashboard, those will be opened once renovate runs again (once every hour)
  • Label all PRs with renovate
  • Use semantic commit messages for all upgrades
  • Open a maximum of 10 PRs concurrently
  • Automatically set reviewers from CODEOWNERS
  • Upgrade arbitrary dependencies in Dockerfiles when you mark them, see the documentation for details
  • Run Renovate on following schedule: every weekday

🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to renovate.json in this branch. Renovate will update the Pull Request description the next time it runs.


What to Expect

With your current configuration, Renovate will create 10 Pull Requests:

chore(deps): update dependency django to v4 [security]
  • Branch name: renovate/pypi-django-vulnerability
  • Merge into: master
  • Upgrade Django to ==4.2.22
chore(deps): update dependency xlrd to v0.9.4
  • Schedule: ["every weekday"]
  • Branch name: renovate/xlrd-0.x
  • Merge into: master
  • Upgrade xlrd to ==0.9.4
chore(deps): update dependency argparse to v1.4.0
  • Schedule: ["every weekday"]
  • Branch name: renovate/argparse-1.x
  • Merge into: master
  • Upgrade argparse to ==1.4.0
chore(deps): update dependency chardet to v2.3.0
  • Schedule: ["every weekday"]
  • Branch name: renovate/chardet-2.x
  • Merge into: master
  • Upgrade chardet to ==2.3.0
chore(deps): update dependency mock to v1.3.0
  • Schedule: ["every weekday"]
  • Branch name: renovate/mock-1.x
  • Merge into: master
  • Upgrade mock to ==1.3.0
chore(deps): update dependency ply to v3.11
  • Schedule: ["every weekday"]
  • Branch name: renovate/ply-3.x
  • Merge into: master
  • Upgrade ply to ==3.11
chore(deps): update dependency simplejson to v3.20.1
  • Schedule: ["every weekday"]
  • Branch name: renovate/simplejson-3.x
  • Merge into: master
  • Upgrade simplejson to ==3.20.1
chore(deps): update dependency chardet to v5
  • Schedule: ["every weekday"]
  • Branch name: renovate/chardet-5.x
  • Merge into: master
  • Upgrade chardet to ==5.2.0
chore(deps): update dependency mock to v5
  • Schedule: ["every weekday"]
  • Branch name: renovate/mock-5.x
  • Merge into: master
  • Upgrade mock to ==5.2.0
chore(deps): update dependency xlrd to v2
  • Schedule: ["every weekday"]
  • Branch name: renovate/xlrd-2.x
  • Merge into: master
  • Upgrade xlrd to ==2.0.2

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

anaconda-renovate[bot] avatar Aug 02 '23 10:08 anaconda-renovate[bot]