chore: Configure Renovate #1

Merged

circuitsacul merged 2 commits from renovate/configure into main

2025-08-14 05:38:14 +00:00

renovate-bot commented

2025-08-14 05:16:25 +00:00

Member

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

act-forgejo/docker-compose.yml (docker-compose)
caddy-proxy/docker-compose.yml (docker-compose)
forgejo/docker-compose.yml (docker-compose)
immich/docker-compose.yml (docker-compose)
nextcloud/docker-compose.yml (docker-compose)

Configuration Summary

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

Start dependency updates only once this onboarding PR is merged
Use semantic prefixes for commit messages and PR titles.
If Renovate detects semantic commits, it will use semantic commit type chore for all commits.
Use semantic commit scope deps for all commits and PR titles.
Use semantic prefixes for commit messages and PR titles.
If Renovate detects semantic commits, it will use semantic commit type chore for all commits.
Use semantic commit scope deps for all commits and PR titles.

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

chore(deps): update docker.io/tensorchord/pgvecto-rs:pg14-v0.2.0 docker digest to 739cdd6

Schedule: ["at any time"]
Branch name: renovate/docker.io-tensorchord-pgvecto-rs-pg14-v0.2.0
Merge into: main
Upgrade docker.io/tensorchord/pgvecto-rs to sha256:739cdd626151ff1f796dc95a6591b55a714f341c737e27f045019ceabf8e8c52

chore(deps): update docker.io/valkey/valkey:8-bookworm docker digest to 5b8f8c3

Schedule: ["at any time"]
Branch name: renovate/docker.io-valkey-valkey-8-bookworm
Merge into: main
Upgrade docker.io/valkey/valkey to sha256:5b8f8c333bef895c925f56629d6ba90aea95a4f7391f62411e625267c600b19c

chore(deps): update codeberg.org/forgejo/forgejo docker tag to v12

Schedule: ["at any time"]
Branch name: renovate/codeberg.org-forgejo-forgejo-12.x
Merge into: main
Upgrade codeberg.org/forgejo/forgejo to 12

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

Welcome to [Renovate](https://github.com/renovatebot/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 * `act-forgejo/docker-compose.yml` (docker-compose) * `caddy-proxy/docker-compose.yml` (docker-compose) * `forgejo/docker-compose.yml` (docker-compose) * `immich/docker-compose.yml` (docker-compose) * `nextcloud/docker-compose.yml` (docker-compose) ### Configuration Summary Based on the default config's presets, Renovate will: - Start dependency updates only once this onboarding PR is merged - Use semantic prefixes for commit messages and PR titles. - If Renovate detects semantic commits, it will use semantic commit type `chore` for all commits. - Use semantic commit scope `deps` for all commits and PR titles. - Use semantic prefixes for commit messages and PR titles. - If Renovate detects semantic commits, it will use semantic commit type `chore` for all commits. - Use semantic commit scope `deps` for all commits and PR titles. 🔡 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 3 Pull Requests: <details> <summary>chore(deps): update docker.io/tensorchord/pgvecto-rs:pg14-v0.2.0 docker digest to 739cdd6</summary> - Schedule: ["at any time"] - Branch name: `renovate/docker.io-tensorchord-pgvecto-rs-pg14-v0.2.0` - Merge into: `main` - Upgrade docker.io/tensorchord/pgvecto-rs to `sha256:739cdd626151ff1f796dc95a6591b55a714f341c737e27f045019ceabf8e8c52` </details> <details> <summary>chore(deps): update docker.io/valkey/valkey:8-bookworm docker digest to 5b8f8c3</summary> - Schedule: ["at any time"] - Branch name: `renovate/docker.io-valkey-valkey-8-bookworm` - Merge into: `main` - Upgrade docker.io/valkey/valkey to `sha256:5b8f8c333bef895c925f56629d6ba90aea95a4f7391f62411e625267c600b19c` </details> <details> <summary>chore(deps): update codeberg.org/forgejo/forgejo docker tag to v12</summary> - Schedule: ["at any time"] - Branch name: `renovate/codeberg.org-forgejo-forgejo-12.x` - Merge into: `main` - Upgrade [codeberg.org/forgejo/forgejo](https://codeberg.org/forgejo/forgejo) to `12` </details> 🚸 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](https://docs.renovatebot.com/), particularly the Getting Started section. If you need any further assistance then you can also [request help here](https://github.com/renovatebot/renovate/discussions). --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).

renovate-bot added 1 commit

2025-08-14 05:16:25 +00:00