Prometheus | v3.14.0

Prometheus v3.14.0 released on 18-08-2026

Prometheus v3.14.0 is out now. Operators and developers get API and service-discovery updates, PromQL and UI/UX improvements, TSDB and remote-protocol fixes, plus a range of reliability and performance patches.

See the Prometheus GitHub release notes or the project website for full details and upgrade guidance.

What’s in this release

• API changes: the /api/v1/query and /api/v1/query_range stats query parameter is deprecated for values other than true and all (other values now emit deprecation warnings and will be rejected in the next major release). The /api/v1/status/config endpoint now shows explicit empty relabel separator: "" and replacement: "".
• PromQL and UI: duration expressions are enabled by default (the promql-duration-expr flag is now a no-op); first_over_time is promoted to stable; new experimental PromQL features are available behind use-start-timestamps (start_timestamp(instant-vector) and using start timestamps for rate()/increase()). The UI adds syntax highlighting, autocompletion and linting for duration expressions and range selectors, plus small UX improvements for rules and alerts.
• Discovery, TSDB and remote: Hetzner metadata label removal and added Oracle Cloud Infrastructure compute discovery (oci_sd_configs); Docker discovery fixes (request timeouts on unix/npipe/tcp hosts, IPv6-only container discovery, and a Swarm panic fix). Experimental TSDB support for encoding histogram start timestamps (behind histograms-st-encoding), remote-write V2 forwarding of histogram start timestamps, new TSDB gauges for native histograms, and several TSDB correctness and performance fixes.

Upgrade notes

• Deprecated API parameter: update any scripts, dashboards or tools that use the stats query parameter with values other than true or all; such values now trigger deprecation warnings and will be rejected in the next major release.
• No special rollback procedure is provided here; if you encounter problems, revert to the previous Prometheus version you were running and file issues with upstream as needed.

Let us know how the upgrade goes — share any issues, regressions or useful improvements you spot when running v3.14.0.