Skip to content

chore(deps): update vmetrics - #2000

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/vmetrics
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/vmetrics

Conversation

@renovate

@renovate renovate Bot commented Oct 13, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Update Change Pending
victoria-metrics-k8s-stack patch 0.95.0 → 0.95.2 0.96.0
victoria-metrics-operator-crds (source) patch 0.15.0 → 0.15.1

Release Notes

VictoriaMetrics/helm-charts (victoria-metrics-k8s-stack)

v0.95.2

Compare Source

Release notes for version 0.95.2

Release date: 07 Oct 2026

Helm: v3 AppVersion: v1.153.0 VM Operator: 0.68.1

  • BUGFIX: fix templates/route.yaml and templates/ingress.yaml failing with vm.operator.kind: appKey "alertmanager" is not vm/vl/vt-prefixed when alertmanager.route.enabled: true or alertmanager.ingress.enabled: true is set. Regression from the victoria-metrics-common 0.4.* bump in v0.95.1, since alertmanager is the only top-level component key that isn't itself vm/vl/vt-prefixed (see #​3270).

v0.95.1

Compare Source

Release notes for version 0.95.1

Release date: 07 Oct 2026

Helm: v3 AppVersion: v1.153.0 VM Operator: 0.68.1

  • bump victoria-metrics-common dependency to 0.4.*. Resource names are unchanged.
  • BUGFIX: preserve user-supplied .Values.alertmanager.config.templates entries instead of overwriting them with the default /etc/vm/templates/**/*.tmpl glob, so custom template paths are no longer silently dropped from the generated config Secret (see #​3266).

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • "before 9am on tuesday"
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled because a matching PR was automerged previously.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@github-actions

Copy link
Copy Markdown
@@ spec.chart.spec.version @@
# helm.toolkit.fluxcd.io/v2/HelmRelease/data/victoria-metrics
! ± value change
- 0.95.0
+ 0.95.2

@@ spec.chart.spec.version @@
# helm.toolkit.fluxcd.io/v2/HelmRelease/monitoring/victoria-metrics
! ± value change
- 0.95.0
+ 0.95.2

@@ spec.chart.spec.version @@
# helm.toolkit.fluxcd.io/v2/HelmRelease/operators/victoria-metrics-crds
! ± value change
- 0.15.0
+ 0.15.1

@@ spec.chart.spec.version @@
# helm.toolkit.fluxcd.io/v2/HelmRelease/monitoring-dev/victoria-metrics-dev
! ± value change
- 0.95.0
+ 0.95.2

@futo-kritika

futo-kritika Bot commented Oct 13, 2026 •

Copy link
Copy Markdown

Re-runKritika Review

Updates VictoriaMetrics stack and operator CRD Helm charts.

No findings

Confidence 4/5 · medium risk: The diff is two patch-level chart bumps (k8s-stack 0.95.0 to 0.95.2 across three monitoring releases, operator CRDs 0.15.0 to 0.15.1), and the review found no problems in them. The stack pulls in a victoria-metrics-common 0.3 to 0.4 minor step that the review checked only for naming, not for template or value-schema changes, so I hold the score just below 5.

Approved

Summary

The change updates all three VictoriaMetrics stack releases to 0.95.2 and the dedicated CRD release to 0.15.1. The upstream fixes are compatible with the configured components, and the CRD update preserves the existing schemas while improving manifest serialization.

Sources consulted

Commands offered: curl, fd, gh, jq, rg, yq; run: rg.

Reviews (1) · Last reviewed commit: "chore(deps): update vmetrics" · openai/gpt-6.1-sol · $0.11

@futo-kritika futo-kritika Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

kritika: confidence 4/5 with medium risk at 119befb.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant