chore: Configure Renovate

[renovate-cynkra]

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/ghcr.yaml (github-actions)

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 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.
• Run lock file maintenance (updates) early Monday mornings.
• Schedule automerge daily.
• Schedule for weekends.
• 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.
• Run lock file maintenance (updates) early Monday mornings.
• Schedule automerge daily.
• Schedule for weekends.
• Run Renovate on following schedule: every weekend

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

chore(deps): update docker/build-push-action digest to 090ca15

• Schedule: ["every weekend"]
• Branch name: renovate/docker-build-push-action-digest
• Merge into: main
• Upgrade docker/build-push-action to 090ca155fc9b214cbcac536c450455a0e96f52c6

chore(deps): update docker/login-action digest to 5f4866a

• Schedule: ["every weekend"]
• Branch name: renovate/docker-login-action-digest
• Merge into: main
• Upgrade docker/login-action to 5f4866a30a54f16a52d2ecb4a3898e9e424939cf

chore(deps): update docker/metadata-action digest to c314eea

• Schedule: ["every weekend"]
• Branch name: renovate/docker-metadata-action-digest
• Merge into: main
• Upgrade docker/metadata-action to c314eea2b27e3cb3c7d7be0618510234d8f6178e

chore(deps): update docker/setup-buildx-action digest to 2b51285

• Schedule: ["every weekend"]
• Branch name: renovate/docker-setup-buildx-action-digest
• Merge into: main
• Upgrade docker/setup-buildx-action to 2b51285047da1547ffb1b2203d8be4c0af6b1f20

chore(deps): update actions/checkout action to v4

• Schedule: ["every weekend"]
• Branch name: renovate/actions-checkout-4.x
• Merge into: main
• Upgrade actions/checkout to v4

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