Catalog / Prometheus

Prometheus breaking changes

The 4 releases whose own notes call out a breaking change, out of 60 the archive holds. Scattered one per release page, this is a run nobody can see; gathered, it is the shape of how often Prometheus asks you to change your code.

Tagged breaking
4of 60 releases
Roughly
1 in 15releases held here
Most recent
17 Oct 202511 months ago
Across
11 monthsback to 14 Nov 2024

How this is decided

A release appears here because the word breaking is in the notes its publisher wrote, not because anyone here read the diff. That cuts both ways. A release that changed an API without using the word is missing from this page, and a release that used the word about something minor is on it. It is the publisher’s own signal, reported rather than judged, which is the same rule the security page follows.

3.7.1breaking

[BUGFIX] OTLP: Prefix key_ to label name when translating an OTel attribute name starting with a single underscore, and keep multiple consecutive underscores in label name when translating an OTel attribute name. This reverts the breaking c

3.7.0breakingaddedchanged

Warning We discovered a breaking change in the OTLP endpoint: OpenTelemetry attribute names starting with underscore, for example _attrib, are no longer automatically translated to key_attrib. Please use 3.7.1 instead for OTLP ingestion. Ch

3.5.0breakingaddedchanged

is a Long Term Support (LTS) release; see release https://prometheus.io/docs/introduction/release-cycle/ There are a number of new features, and no known breaking changes in this release: [FEATURE] PromQL: Add experimental type and unit met

3.0.0breakingaddedfixed

This release includes new features such as a brand new UI and UTF-8 support enabled by default. As this marks the first new major version in seven years, several breaking changes are introduced. The breaking changes are mainly around the re