Skip to content

chore: Configure Renovate#1

Merged
filiplajszczak merged 1 commit intomasterfrom
renovate/configure
Feb 27, 2026
Merged

chore: Configure Renovate#1
filiplajszczak merged 1 commit intomasterfrom
renovate/configure

Conversation

@anaconda-renovate
Copy link
Contributor

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

  • .github/workflows/release.yml (github-actions)
  • .github/workflows/test.yml (github-actions)
  • pyproject.toml (pep621)
  • .pre-commit-config.yaml (pre-commit)
  • 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 6 Pull Requests:

chore(deps): update actions/checkout action to v6.0.2
  • Schedule: ["every weekday"]
  • Branch name: renovate/actions-checkout-6.x
  • Merge into: master
  • Upgrade actions/checkout to de0fac2e4500dabe0009e67214ff5f5447ce83dd
chore(deps): update pre-commit hook astral-sh/ruff-pre-commit to v0.15.4
  • Schedule: ["every weekday"]
  • Branch name: renovate/astral-sh-ruff-pre-commit-0.x
  • Merge into: master
  • Upgrade astral-sh/ruff-pre-commit to v0.15.4
chore(deps): update astral-sh/setup-uv action to v6.8.0
  • Schedule: ["every weekday"]
  • Branch name: renovate/astral-sh-setup-uv-6.x
  • Merge into: master
  • Upgrade astral-sh/setup-uv to d0cc045d04ccac9d8b7881df0226f9e82c39688e
chore(deps): update dependency uv_build to >=0.10.6, <0.11
  • Schedule: ["every weekday"]
  • Branch name: renovate/uv_build-0.x
  • Merge into: master
  • Upgrade uv_build to >=0.10.6, <0.11
chore(deps): update astral-sh/setup-uv action to v7
  • Schedule: ["every weekday"]
  • Branch name: renovate/astral-sh-setup-uv-7.x
  • Merge into: master
  • Upgrade astral-sh/setup-uv to eac588ad8def6316056a12d4907a9d4d84ff7a3b
chore(deps): update github artifact actions (major)
  • Schedule: ["every weekday"]
  • Branch name: renovate/major-github-artifact-actions
  • Merge into: master
  • Upgrade actions/download-artifact to 70fc10c6e5e1ce46ad2ea6f2b72d43f7d47b13c3
  • Upgrade actions/upload-artifact to bbbca2ddaa5d8feaa63e36b76fdaad77386f024f

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

@filiplajszczak filiplajszczak merged commit 6baa73d into master Feb 27, 2026
12 checks passed
@anaconda-renovate anaconda-renovate bot deleted the renovate/configure branch February 27, 2026 15:14
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.

1 participant