This is a bug-fix release, reverting a change introduced in v2.52.0. The bug was that Prometheus could crash with a segmentation fault if a remote-read request accessed a block on disk at about the same time as TSDB created a new block. The issue is #14422.
Many thanks to GitHub user 'fbs' for diligently bisecting the source of the problem. Changelog and binaries are available at https://github.com/prometheus/prometheus/releases/tag/v2.53.2 As usual, container images are available at https://quay.io/repository/prometheus/prometheus?tab=tags and https://hub.docker.com/r/prom/prometheus/tags Regards, Bryan Boreham (@bboreham) -- You received this message because you are subscribed to the Google Groups "prometheus-announce" group. To unsubscribe from this group and stop receiving emails from it, send an email to prometheus-announce+unsubscr...@googlegroups.com. To view this discussion on the web, visit https://groups.google.com/d/msgid/prometheus-announce/e4769660-728c-4682-a8fa-c35969cf9c59n%40googlegroups.com.
