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:

VictoriaMetrics May 2026 Ecosystem Updates

May 2026 VictoriaMetrics release roundup: v1.144.0 brings 15 bug fixes and 9 UX improvements for reliability and observability, while v1.143.0 adds native Prometheus histogram ingestion support across vmagent, vmsingle, and vminsert. Also includes the first LTS release for VictoriaMetrics Operator.

Operator now has Long-Term Support (LTS) version

VictoriaMetrics Operator introduces Long-Term Support (LTS) releases starting with v0.68.x, ensuring stability and a predictable upgrade path for users.

How Airbnb Built a High-Volume Metrics Pipeline with OpenTelemetry and vmagent

Learn how Airbnb rebuilt its observability pipeline with OpenTelemetry and vmagent to handle over 100 million samples per second, reduce cost by 10x, and simplify high-scale metrics aggregation.

Multi-tiered Observability: A Practical Way to Handle Diverse Workloads

Discover multi-tier observability architecture with VictoriaMetrics OSS. Learn how to isolate default, high-cardinality, and business-critical workloads into separate tiers with optimized retention periods, ingestion resolution, cardinality limits, alerting policies, and cost controls.