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:

VictoriaLogs Basics: What You Need to Know, with Examples & Visuals

Cluster mode in VictoriaLogs is not a separate build. It is the same victoria-logs binary started with different flags, so you can scale out without a migration step. Storage nodes persist data on disk, while gateway nodes can stay stateless by pointing to storage with -storageNode. It also ships with practical safety switches, like read-only protection when -storageDataPath runs low and optional partial results when a storage node is down.

What's New in VictoriaMetrics Cloud Q4 2025? New tiers, more deployment options, IaC and alerting rules.

In the last quarter of 2025, VictoriaMetrics Cloud brings many great features: New powerful Capacity Tiers, the expansion to the us-east-1 (N.Virginia) AWS region in the US, new Notification Groups, a Terraform provider to complete your IaC, 9 brand new Alerting Rule Integrations and much more.

Vibe coding tools observability with VictoriaMetrics Stack and OpenTelemetry

Learn how to add observability to Vibe Coding Tools using OpenTelemetry and the VictoriaMetrics Stack. This guide explains how to configure popular vibe coding tools to export their metrics telemetry and get insights about your vibe coding sessions.

How a US Software Provider Improved Traffic Alerting with VictoriaMetrics Anomaly Detection

VictoriaMetrics Anomaly Detection enables reliable alerting for highly variable, multi-domain traffic without relying on static thresholds. In this case study, fine-tuned models, backtesting, and clear visualization helped reduce alert noise, improve confidence in anomaly detection, and lower operational overhead.