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

• Dockerfile (dockerfile)
• .github/workflows/cicd.yml (github-actions)

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.

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

Update actions/checkout action to v3.6.0

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

Update docker/build-push-action action to v3.3.1

• Schedule: ["at any time"]
• Branch name: renovate/docker-build-push-action-3.x
• Merge into: main
• Upgrade docker/build-push-action to v3.3.1

Update docker/login-action action to v2.2.0

• Schedule: ["at any time"]
• Branch name: renovate/docker-login-action-2.x
• Merge into: main
• Upgrade docker/login-action to v2.2.0

Update docker/metadata-action action to v4.6.0

• Schedule: ["at any time"]
• Branch name: renovate/docker-metadata-action-4.x
• Merge into: main
• Upgrade docker/metadata-action to v4.6.0

Update docker/setup-buildx-action action to v2.10.0

• Schedule: ["at any time"]
• Branch name: renovate/docker-setup-buildx-action-2.x
• Merge into: main
• Upgrade docker/setup-buildx-action to v2.10.0

Update docker/setup-qemu-action action to v2.2.0

• Schedule: ["at any time"]
• Branch name: renovate/docker-setup-qemu-action-2.x
• Merge into: main
• Upgrade docker/setup-qemu-action to v2.2.0

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

Update debian Docker tag to v12

• Schedule: ["at any time"]
• Branch name: renovate/debian-12.x
• Merge into: main
• Upgrade debian to bookworm

Update docker/build-push-action action to v5

• Schedule: ["at any time"]
• Branch name: renovate/docker-build-push-action-5.x
• Merge into: main
• Upgrade docker/build-push-action to v5.1.0

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

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

Update docker/setup-buildx-action action to v3

• Schedule: ["at any time"]
• Branch name: renovate/docker-setup-buildx-action-3.x
• Merge into: main
• Upgrade docker/setup-buildx-action to v3.0.0

Update docker/setup-qemu-action action to v3

• Schedule: ["at any time"]
• Branch name: renovate/docker-setup-qemu-action-3.x
• Merge into: main
• Upgrade docker/setup-qemu-action to v3.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 has been generated by Mend Renovate. View repository job log here.