ci(renovate): change docker compose settings

[falo2k]

No description provided.

[renovate]

Reconfigure PR Results

This is a reconfigure PR comment to help you understand and re-configure your renovate bot settings. If this Reconfigure PR were to be merged, we'd expect to see the following outcome:

---

Detected Package Files

• docker-compose.caddy.yml (docker-compose)
• docker-compose.dev.yml (docker-compose)
• docker-compose.yml (docker-compose)
• Dockerfile (dockerfile)
• Dockerfile.caddy (dockerfile)
• Dockerfile.dev (dockerfile)
• .github/workflows/docker-build-branch.yml (github-actions)
• .github/workflows/docker-build.yml (github-actions)
• .github/workflows/docker-cleanup-deleted-branches.yml (github-actions)
• .github/workflows/release-please.yml (github-actions)
• .github/workflows/test.yml (github-actions)
• pyproject.toml (pep621)

Configuration Summary

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

• 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.
• Ensure that every dependency pinned by digest and sourced from Forgejo contains a link to the commit-to-commit diff
• Ensure that every dependency pinned by digest and sourced from Gitea contains a link to the commit-to-commit diff
• Ensure that every dependency pinned by digest and sourced from GitHub.com and Github enterprise contains a link to the commit-to-commit diff
• Correctly link to the source code for golang.org/x packages
• Link to pkg.go.dev/... for golang.org/x packages' title
• Weekly schedule on early Monday mornings (before 4 AM).
• Pin github-action digests.
• Enable Renovate configuration migration PRs when needed.
• Pin dependency versions for development dependencies.
• Recommended configuration for abandoned packages, treating packages without a release for 1 year as abandoned, while taking into account community-sourced overrides.
• Run lock file maintenance (updates) early Monday mornings.
• Group all digest updates together.
• Run Renovate on following schedule: * 0-3 * * 1

---

What to Expect

With your current configuration, Renovate will create 1 Pull Request:

chore(deps): lock file maintenance

• Schedule: ["* 0-3 * * 1"]
• Branch name: renovate/lock-file-maintenance
• Merge into: master
• Regenerate lock files to use latest dependency versions