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

• docker/deprecated-images/build-kit/alpine.Dockerfile (dockerfile)
• docker/deprecated-images/build-kit/debian.Dockerfile (dockerfile)
• docker/deprecated-images/everest-clang-format/Dockerfile (dockerfile)
• docker/images/build-env-base/Dockerfile (dockerfile)
• docker/images/build-kit-base/Dockerfile (dockerfile)
• docker/images/dev-env-base/Dockerfile (dockerfile)
• docker/images/run-env-base/Dockerfile (dockerfile)
• .github/workflows/deploy-docker-images.yml (github-actions)
• .github/workflows/deploy-single-docker-image.yml (github-actions)
• scripts/ci-tools/pyproject.toml (pep621)
• scripts/ci-tools/setup.cfg (setup-cfg)
• github-actions/run-clang-format/action.yaml (regex)

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 10 Pull Requests:

Update ghcr.io/everest/everest-ci/build-env-base Docker tag to v1.3.1

• Schedule: ["at any time"]
• Branch name: renovate/ghcr.io-everest-everest-ci-build-env-base-1.x
• Merge into: main
• Upgrade ghcr.io/everest/everest-ci/build-env-base to v1.3.1

Update alpine Docker tag to v3.20

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

Update debian Docker tag to v11.10

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

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

Update debian Docker tag to v12

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

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

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

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

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

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

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