Skip to content

Configure Renovate#1

Open
tjboller wants to merge 1 commit intomainfrom
renovate/configure
Open

Configure Renovate#1
tjboller wants to merge 1 commit intomainfrom
renovate/configure

Conversation

@tjboller
Copy link

@tjboller tjboller commented Dec 16, 2025

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

  • pyproject.toml (pep621)
  • .pre-commit-config.yaml (pre-commit)

Configuration Summary

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

  • Start dependency updates only once this onboarding PR is merged
  • 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 (except for nuget) directories.
  • Group known monorepo packages together.
  • Use curated list of recommended non-monorepo package groupings.
  • Show only the Age and Confidence Merge Confidence badges for pull requests.
  • Apply crowd-sourced package replacement rules.
  • Apply crowd-sourced workarounds for known problems with packages.
  • Pin Docker digests.
  • Pin github-action digests.
  • Enable Renovate configuration migration PRs when needed.
  • Pin dependency versions for development dependencies.
  • Recommended configuration for abandoned packages, treating packages without a release for 1 year as abandoned, while taking into account community-sourced overrides.
  • Rebase existing PRs any time the base branch has been updated.
  • Preserve (but continue to upgrade) any existing SemVer ranges.
  • Separate each major version of dependencies into individual branches/PRs.
  • Raise PR when vulnerability alerts are detected.
  • Weekly schedule on early Monday mornings (before 4 AM).
  • 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 (except for nuget) directories.
  • Group known monorepo packages together.
  • Use curated list of recommended non-monorepo package groupings.
  • Show only the Age and Confidence Merge Confidence badges for pull requests.
  • Apply crowd-sourced package replacement rules.
  • Apply crowd-sourced workarounds for known problems with packages.
  • Pin Docker digests.
  • Pin github-action digests.
  • Enable Renovate configuration migration PRs when needed.
  • Pin dependency versions for development dependencies.
  • Recommended configuration for abandoned packages, treating packages without a release for 1 year as abandoned, while taking into account community-sourced overrides.
  • Rebase existing PRs any time the base branch has been updated.
  • Preserve (but continue to upgrade) any existing SemVer ranges.
  • Separate each major version of dependencies into individual branches/PRs.
  • Raise PR when vulnerability alerts are detected.
  • Weekly schedule on early Monday mornings (before 4 AM).
  • Run Renovate on following schedule: * 0-3 * * 1

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


What to Expect

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

Update pre-commit hook charliermarsh/ruff-pre-commit to v0.14.9
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/charliermarsh-ruff-pre-commit-0.x
  • Merge into: main
  • Upgrade charliermarsh/ruff-pre-commit to v0.14.9
Update pre-commit hook pre-commit/pre-commit-hooks to v4.6.0
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/pre-commit-pre-commit-hooks-4.x
  • Merge into: main
  • Upgrade pre-commit/pre-commit-hooks to v4.6.0
Update pre-commit hook psf/black to v23.12.1
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/psf-black-23.x
  • Merge into: main
  • Upgrade psf/black to 23.12.1
Update pre-commit hook python-poetry/poetry to v1.8.5
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/python-poetry-poetry-1.x
  • Merge into: main
  • Upgrade python-poetry/poetry to 1.8.5
Update pre-commit hook pre-commit/pre-commit-hooks to v5
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/pre-commit-pre-commit-hooks-5.x
  • Merge into: main
  • Upgrade pre-commit/pre-commit-hooks to v5.0.0
Update pre-commit hook pre-commit/pre-commit-hooks to v6
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/pre-commit-pre-commit-hooks-6.x
  • Merge into: main
  • Upgrade pre-commit/pre-commit-hooks to v6.0.0
Update pre-commit hook psf/black to v24
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/psf-black-24.x
  • Merge into: main
  • Upgrade psf/black to 24.10.0
Update pre-commit hook psf/black to v25
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/psf-black-25.x
  • Merge into: main
  • Upgrade psf/black to 25.12.0
Update pre-commit hook python-poetry/poetry to v2
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/python-poetry-poetry-2.x
  • Merge into: main
  • Upgrade python-poetry/poetry to 2.2.1

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


  • If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Renovate Bot.


Note

Add renovate.json configuring Renovate via local>enveda/renovate-config preset.

Written by Cursor Bugbot for commit 3f11794. This will update automatically on new commits. Configure here.

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants