Configure Renovate #1

Merged

pieter merged 1 commit from renovate/configure into main

2026-01-22 18:01:52 +01:00

renovate-bot commented

2026-01-22 18:00:40 +01:00

Collaborator

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/compose.with-database-grafana.yml (docker-compose)
docker/compose.with-database.yml (docker-compose)
docker/compose.yml (docker-compose)
Dockerfile (dockerfile)
.forgejo/workflows/docker.yml (github-actions)
.forgejo/workflows/go.yml (github-actions)
go.mod (gomod)

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 (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 GitHub.com 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

🔡 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:

Update actions/checkout action to v6

Schedule: ["at any time"]
Branch name: renovate/actions-checkout-6.x
Merge into: main
Upgrade actions/checkout to v6

Update actions/setup-go action to v6

Schedule: ["at any time"]
Branch name: renovate/actions-setup-go-6.x
Merge into: main
Upgrade actions/setup-go to v6

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

🚸 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 * `docker/compose.with-database-grafana.yml` (docker-compose) * `docker/compose.with-database.yml` (docker-compose) * `docker/compose.yml` (docker-compose) * `Dockerfile` (dockerfile) * `.forgejo/workflows/docker.yml` (github-actions) * `.forgejo/workflows/go.yml` (github-actions) * `go.mod` (gomod) ### 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 (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 GitHub.com 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 🔡 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>Update actions/checkout action to v6</summary> - Schedule: ["at any time"] - Branch name: `renovate/actions-checkout-6.x` - Merge into: `main` - Upgrade [actions/checkout](https://github.com/actions/checkout) to `v6` </details> <details> <summary>Update actions/setup-go action to v6</summary> - Schedule: ["at any time"] - Branch name: `renovate/actions-setup-go-6.x` - Merge into: `main` - Upgrade [actions/setup-go](https://github.com/actions/setup-go) to `v6` </details> <details> <summary>Update docker/build-push-action action to v6</summary> - Schedule: ["at any time"] - Branch name: `renovate/docker-build-push-action-6.x` - Merge into: `main` - Upgrade [docker/build-push-action](https://github.com/docker/build-push-action) to `v6` </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

2026-01-22 18:00:40 +01:00