Thanos v0.42.4 contains no described operator-facing changes in the supplied release information. The available note is a duplicate mention.
Source ↗Releases
AI-analyzed release notes for CNCF graduated and incubating projects.
This release contains a receive shutdown regression correction. Blocks are uploaded before TSDB shutdown completes, preserving upload behavior during shutdown.
Source ↗Thanos v0.42.2 contains no reported operator-facing changes. There are no release-note updates that affect configuration, operation, or user-visible behavior.
Source ↗This release corrects overly small timeouts in the Receiver's Shipper component. The available release information does not include a recorded change item to describe in more detail.
Source ↗A release with security corrections, breaking configuration removals, and an output-field rename that may require operator or log-collector changes. It also adds TLS and cache configuration, query and tracing changes, and defect fixes across several Thanos components.
Action needed (1)
securitycritical
thanos-community/grpc-gofork update for CVE-2026-33186The
thanos-community/grpc-gofork is bumped to fix CVE-2026-33186, an authorization bypass via malformed:pathheaders.
Check if affected (4)
security
Receivetenant ID validationApplies if you run
Receive.Receivevalidates tenant IDs extracted from split-tenant labels to prevent path traversal.breaking
Query-Frontendtime_takenfield renamed totime_taken_msApplies if you run
Query-Frontend.The
Query-FrontendJSON output now usestime_taken_msinstead oftime_taken, for consistent output and easier parsing by log collectors.breaking
--shipper.flag removedignore-unequal-block-size Applies if you configure
--shipper..ignore-unequal-block-size The breaking
--shipper.flag is removed fromignore-unequal-block-size Receive.- + 1 more on the release page
This release combines performance improvements, bug fixes, and new configuration capabilities with a shuffle-sharding behavior change in Receive. It also upgrades Prometheus, deprecates a flag, and makes native histogram ingestion always enabled.
Check if affected (1)
breaking
Receiveshuffle sharding now uses consistent hashingApplies if you use
Receive.In
Receive, shuffle sharding now uses consistent hashing for stability on scale. Existing tenant-to-node assignments change on upgrade.