1. Blog
    2. /
  2. VictoriaMetrics Long-Term Support (LTS): Commitment, Current and Next LTS Versions
VictoriaMetrics Long-Term Support (LTS): Commitment, Current and Next LTS Versions

VictoriaMetrics Long-Term Support (LTS): Commitment, Current and Next LTS Versions

Share: Share on LinkedIn Share on X (Twitter)

VictoriaMetrics is always improving, with frequent updates adding new features, performance improvements and bug fixes listed at the CHANGELOG page. We usually make at least a single release every month. All the new features and bug fixes go to the latest release. That’s why we recommend periodically upgrading VictoriaMetrics components to the latest available release. But the latest release may also contain bugs in the latest features. So we decided to start publishing Long-term support releases (LTS) on top of usual releases, which contain only bug fixes without new features and performance improvements.

Our Commitment

#

We are committed to supporting every LTS release for a year and marking one of our releases as LTS every 6 months.

This allows our users, who prefer stability over new features and performance improvements, to stay on LTS releases. There is a 6 months overlap between LTS releases, which gives enough time for the upgrade to the next LTS release.

The current LTS release: v1.79.x

#

In July 2022, we cut the LTS version, which is v1.79.x release. This release was explicitly marked as LTS on Github, and its latest version is v1.79.8. This release includes all the important bug fixes from the subsequent releases listed at the CHANGELOG.

The v1.79.x line of releases will stop receiving new bug fixes after July 2023.

The next LTS release: v1.87.x

#

We are going to mark the v1.87.x release as the next LTS. It will receive bug fixes until January 2024. Both v1.87.x and v1.79.x releases will receive bug fixes during the next 6 months.

Upgrade from v1.79.x to v1.87.x

#

It is recommended to read the CHANGELOG between these releases before the upgrade in order to be prepared for new features or issues. It is OK to upgrade from v1.79.x to v1.87.x according to these docs. If you are going to upgrade the VictoriaMetrics cluster, then please read these docs. In case of unlikely issues it is OK to downgrade from v1.87.x to v1.79.x.

We suggest upgrading the Grafana dashboards and alerting rules for VictoriaMetrics components, since they contain various improvements with each release.

Leave a comment below or Contact Us if you have any questions!
comments powered by Disqus

You might also like:

What's new in VictoriaMetrics Anomaly Detection (Q1 2026)

Q1 2026 brought incremental but important updates to VictoriaMetrics Anomaly Detection: UI improvements, AI assistance inside the UI, a public traces playground, new false-positive reduction controls, and continued resource optimizations.

VictoriaMetrics at KubeCon Amsterdam: Community Highlights

VictoriaMetrics participated in KubeCon + CloudNativeCon Europe 2026 in Amsterdam. The team delivered multiple talks covering platform design, Kubernetes observability, and distributed tracing optimization. A real-world case study from Miro showcased a cost-efficient, AZ-aware observability architecture built with VictoriaMetrics. With a 15-person team on site, the booth saw strong interest from users tackling scaling, cost, and performance challenges. The company also hosted its first community after-party, “After Deploy,” co-organized with Varnish and Shipfox, extending discussions beyond the conference.

What's New in VictoriaMetrics Cloud Q1 2026? Logs, MCP Server, Better Alerting, and... a Secret Project

Q1 2026 brought VictoriaLogs GA, a hosted MCP Server, a brand new cost calculator, a major expansion of alerting rule presets with a new editor, infrastructure improvements, notifications via generic webhooks and a few things we are cooking.

VictoriaMetrics at KubeCon: Optimizing Tail Sampling in OpenTelemetry with Retroactive Sampling

If you’ve been struggling with the high resource overhead of tail sampling, check out retroactive sampling, an approach that significantly reduces sampling overhead for distributed tracing in OpenTelemetry.