coop-cloud/monitoring-ng
1
0
Fork 2
Code Issues 7 Pull Requests 5 Packages Projects Releases Wiki Activity

chore: Configure Renovate #11

Open
renovate-bot wants to merge 1 commits from renovate/configure into main
pull from: renovate/configure
merge into: :main
Conversation 1 Commits 1 Files Changed 1
+6
renovate-bot commented 2026-03-10 17:55:51 +00:00
Member
Copy Link
Copy Source

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

  • compose.expose-ports.yml (docker-compose)
  • compose.grafana-oidc.yml (docker-compose)
  • compose.grafana-smtp.yml (docker-compose)
  • compose.grafana.yml (docker-compose)
  • compose.loki.yml (docker-compose)
  • compose.matrix-alertmanager-receiver.yml (docker-compose)
  • compose.prometheus.yml (docker-compose)
  • compose.promtail.yml (docker-compose)
  • compose.pushgateway.yml (docker-compose)
  • 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
  • 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.

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

chore(deps): update grafana/grafana docker tag to v12.4.9
  • Schedule: ["at any time"]
  • Branch name: renovate/grafana-monorepo
  • Merge into: main
  • Upgrade grafana/grafana to 12.4.9
chore(deps): update grafana/promtail docker tag to v3.6.11
  • Schedule: ["at any time"]
  • Branch name: renovate/grafana-promtail-3.x
  • Merge into: main
  • Upgrade grafana/promtail to 3.6.11
chore(deps): update prom/pushgateway docker tag to v1.11.3
  • Schedule: ["at any time"]
  • Branch name: renovate/prom-pushgateway-1.x
  • Merge into: main
  • Upgrade prom/pushgateway to v1.11.3
chore(deps): update grafana/loki docker tag to v3.7.6
  • Schedule: ["at any time"]
  • Branch name: renovate/grafana-loki-3.x
  • Merge into: main
  • Upgrade grafana/loki to 3.7.6
chore(deps): update metio/matrix-alertmanager-receiver docker tag to v2026.8.5
chore(deps): update prom/node-exporter docker tag to v1.12.1
  • Schedule: ["at any time"]
  • Branch name: renovate/prom-node-exporter-1.x
  • Merge into: main
  • Upgrade prom/node-exporter to v1.12.1
chore(deps): update prom/prometheus docker tag to v3.14.0
  • Schedule: ["at any time"]
  • Branch name: renovate/prom-prometheus-3.x
  • Merge into: main
  • Upgrade prom/prometheus to v3.14.0
chore(deps): update grafana/grafana docker tag to v13
  • Schedule: ["at any time"]
  • Branch name: renovate/major-grafana-monorepo
  • Merge into: main
  • Upgrade grafana/grafana to 13.2.0

🚸 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 * `compose.expose-ports.yml` (docker-compose) * `compose.grafana-oidc.yml` (docker-compose) * `compose.grafana-smtp.yml` (docker-compose) * `compose.grafana.yml` (docker-compose) * `compose.loki.yml` (docker-compose) * `compose.matrix-alertmanager-receiver.yml` (docker-compose) * `compose.prometheus.yml` (docker-compose) * `compose.promtail.yml` (docker-compose) * `compose.pushgateway.yml` (docker-compose) * `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 - 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. 🔡 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 8 Pull Requests: <details> <summary>chore(deps): update grafana/grafana docker tag to v12.4.9</summary> - Schedule: ["at any time"] - Branch name: `renovate/grafana-monorepo` - Merge into: `main` - Upgrade [grafana/grafana](https://github.com/grafana/grafana) to `12.4.9` </details> <details> <summary>chore(deps): update grafana/promtail docker tag to v3.6.11</summary> - Schedule: ["at any time"] - Branch name: `renovate/grafana-promtail-3.x` - Merge into: `main` - Upgrade grafana/promtail to `3.6.11` </details> <details> <summary>chore(deps): update prom/pushgateway docker tag to v1.11.3</summary> - Schedule: ["at any time"] - Branch name: `renovate/prom-pushgateway-1.x` - Merge into: `main` - Upgrade prom/pushgateway to `v1.11.3` </details> <details> <summary>chore(deps): update grafana/loki docker tag to v3.7.6</summary> - Schedule: ["at any time"] - Branch name: `renovate/grafana-loki-3.x` - Merge into: `main` - Upgrade grafana/loki to `3.7.6` </details> <details> <summary>chore(deps): update metio/matrix-alertmanager-receiver docker tag to v2026.8.5</summary> - Schedule: ["at any time"] - Branch name: `renovate/metio-matrix-alertmanager-receiver-2026.x` - Merge into: `main` - Upgrade [metio/matrix-alertmanager-receiver](https://github.com/metio/matrix-alertmanager-receiver) to `2026.8.5` </details> <details> <summary>chore(deps): update prom/node-exporter docker tag to v1.12.1</summary> - Schedule: ["at any time"] - Branch name: `renovate/prom-node-exporter-1.x` - Merge into: `main` - Upgrade [prom/node-exporter](https://github.com/prometheus/node_exporter) to `v1.12.1` </details> <details> <summary>chore(deps): update prom/prometheus docker tag to v3.14.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/prom-prometheus-3.x` - Merge into: `main` - Upgrade [prom/prometheus](https://github.com/prometheus/prometheus) to `v3.14.0` </details> <details> <summary>chore(deps): update grafana/grafana docker tag to v13</summary> - Schedule: ["at any time"] - Branch name: `renovate/major-grafana-monorepo` - Merge into: `main` - Upgrade [grafana/grafana](https://github.com/grafana/grafana) to `13.2.0` </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-config-hash:e80b4e42a3043bc12fa0640db4bac392d2bf770acf841360d7c8ceeeac2ec1a9-->
renovate-bot added 1 commit 2026-03-10 17:55:51 +00:00
Add renovate.json 60044473cb
p4u1 commented 2026-03-20 09:25:38 +00:00
Owner
Copy Link
Copy Source

Let's wait until we merge #10 otherwise there will be a lot of noise

Let's wait until we merge https://git.coopcloud.tech/coop-cloud/monitoring-ng/pulls/10 otherwise there will be a lot of noise
You are not authorized to merge this pull request.
This pull request can be merged automatically.
This branch is out-of-date with the base branch
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin renovate/configure:renovate/configure
git checkout renovate/configure
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
3wordchant aadil (Aadil Ayub) abra-bot (Abra Bot) ammaratef45 amras (Sarma) BornDeleuze Brooke cas (Cassowary) coopcloud dannygroenewegen (Danny Groenewegen) decentral1se (d1) fauno (fauno) jjsfunhouse kawaiipunk (KawaiiPunk) knoflook moosemower moritz notplants oxaliq (sorrel) p4u1 renovate-bot (Comrade Renovate Bot) stevensting trav (Trav Fryer) yksflip
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: coop-cloud/monitoring-ng#11