Prometheus 3.15.0 went out on September 25, 2026, and almost nobody in the CNCF ecosystem noticed the release that matters most to them. That is not marketing speak — it is the actual risk profile of this release. The changelog reads as a routine minor: a scrape-format addition, a long-awaited socket feature, a storage-encoding promotion. Buried in the bugfix list, though, sits PR #19700: a fix for a failure mode where a failed WAL write in Agent mode could return a dirty buffer to the pool, and a later append could concatenate a new record with the corpse of the failed one — producing a WAL record that passes its checksum and is structurally invalid. That is the quietest data-corruption class there is: no crash, no log line at write time, just a segment your future self cannot replay. This is the release analysis for people who run Prometheus in anger, not people who read feature lists.

The Bug Nobody Upgrades For: Agent-Mode WAL Corruption

Agent mode — the scrape-and-forward configuration where Prometheus keeps no local query path and streams samples via remote write — lives and dies by its write-ahead log. Every sample batch is appended to the WAL before it is shipped; on restart, the WAL replay is the difference between a blip and a data-loss incident. The bug fixed by PR #19700 (authored by @fancive, merged September 16, days before the release cut) is in the error path of that append, which is exactly where nobody looks until a disk fills up:

Normal append:   log(rec) ─▶ WAL page write OK ─▶ buffer(len=N) ─▶ back to pool

Failed append:   log(rec) ─▶ WAL page write FAILS
                                  │
   pre-3.15:                      └─▶ buffer returned to the shared pool
                                       STILL HOLDING the partially-encoded
                                       failed record
                                            │
                                       next append reuses that buffer:
                                       new record bytes CONCATENATED with
                                       the failed record's remnant
                                            │
                                       result: a WAL record that
                                       CHECKSUMS but is structurally
                                       invalid on replay

3.15 (#19700):    all error paths in log() and logSeries() return buffers
                  to the pool with ZERO length — reuse starts clean