Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: Configure Renovate #1

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

chore: Configure Renovate #1

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Aug 26, 2024

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)
  • .github/workflows/docker-build-push.yml (github-actions)
  • pyproject.toml (pep621)
  • pyproject.toml (poetry)

Configuration Summary

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

  • Start dependency updates only once this onboarding PR is merged
  • Show all Merge Confidence badges for pull requests.
  • Enable Renovate Dependency Dashboard creation.
  • Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.
  • Ignore node_modules, bower_components, vendor and various test/tests directories.
  • Group known monorepo packages together.
  • Use curated list of recommended non-monorepo package groupings.
  • Apply crowd-sourced package replacement rules.
  • Apply crowd-sourced workarounds for known problems with packages.
  • Enable Docker major updates.
  • Run lock file maintenance (updates) on the first day of each month.
  • Enable Renovate Dependency Dashboard creation.
  • Preserve (but continue to upgrade) any existing SemVer ranges.
  • Rate limit PR creation to a maximum of four per hour.
  • Use semantic prefixes for commit messages and PR titles.
  • Evaluate schedules according to timezone Europe/Paris.

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

chore(deps): update actions/checkout action to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-checkout-4.x
  • Merge into: main
  • Upgrade actions/checkout to v4
chore(deps): update dependency pytest to v8
  • Schedule: ["at any time"]
  • Branch name: renovate/pytest-8.x
  • Merge into: main
  • Upgrade pytest to ^8.0.0
chore(deps): update docker/build-push-action action to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/docker-build-push-action-6.x
  • Merge into: main
  • Upgrade docker/build-push-action to v6
chore(deps): update docker/login-action action to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/docker-login-action-3.x
  • Merge into: main
  • Upgrade docker/login-action to v3
chore(deps): update docker/metadata-action action to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/docker-metadata-action-5.x
  • Merge into: main
  • Upgrade docker/metadata-action to v5
chore(deps): lock file maintenance
  • Schedule: ["before 4am on the first day of the month"]
  • Branch name: renovate/lock-file-maintenance
  • Merge into: main
  • Regenerate lock files to use latest dependency versions

🚸 Branch creation will be limited to maximum 4 per hour, so it doesn't swamp any CI resources or overwhelm 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 was generated by Mend Renovate. View the repository job log.

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

Successfully merging this pull request may close these issues.

0 participants