Configure Renovate

[renovate]

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/check_libs.yaml (github-actions)
• .github/workflows/ci.yaml (github-actions)
• .github/workflows/release.yaml (github-actions)
• pyproject.toml (poetry)

Configuration Summary

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

• Start dependency updates only once this onboarding PR is merged
• Hopefully safe environment variables to allow users to configure.
• 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 (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.

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

Update canonical/data-platform-workflows action to v32.2.3

• Schedule: ["at any time"]
• Branch name: renovate/canonical-data-platform-workflows-32.x
• Merge into: main
• Upgrade canonical/data-platform-workflows to v32.2.3

Update canonical/charming-actions action to v2.7.0

• Schedule: ["at any time"]
• Branch name: renovate/canonical-charming-actions-2.x
• Merge into: main
• Upgrade canonical/charming-actions to 2.7.0

Update dependency ops to v2.23.1

• Schedule: ["at any time"]
• Branch name: renovate/ops-2.x-lockfile
• Merge into: main
• Upgrade ops to 2.23.1

Update actions/checkout action to v5

• Schedule: ["at any time"]
• Branch name: renovate/actions-checkout-5.x
• Merge into: main
• Upgrade actions/checkout to v5

Update canonical/data-platform-workflows action to v35

• Schedule: ["at any time"]
• Branch name: renovate/canonical-data-platform-workflows-35.x
• Merge into: main
• Upgrade canonical/data-platform-workflows to v35.0.2

Update dependency ops to v3

• Schedule: ["at any time"]
• Branch name: renovate/ops-3.x
• Merge into: main
• Upgrade ops to ^3.0.0

Update dependency ops to v3

• Schedule: ["at any time"]
• Branch name: renovate/ops-3.x-lockfile
• Merge into: main
• Upgrade ops to 3.2.0

Update dependency tenacity to v9

• Schedule: ["at any time"]
• Branch name: renovate/tenacity-9.x
• Merge into: main
• Upgrade tenacity to ^9.0.0

🚸 Branch creation will be limited to maximum 2 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.

[taurus-forever]

🌟 @paulomach IMHO, we should enable renovate here to have common CI.
@carlcsaposs-canonical can you share with @shayancanonical the snared DPE renovate config examples.

[carlcsaposs-canonical]

@shayancanonical https://github.com/canonical/data-platform/tree/main/renovate_presets