v26.40.1 release notes - #38675
Open
bosconi wants to merge 1 commit into
Open
Conversation
Adds the `## v26.40.1` section to the releases index and a row to the Self-Managed operator compatibility table. v26.40.1 is a three-commit hotfix train with no RC snapshots, so this one commit carries the whole release note: two metric-cardinality entries (#38614, #38640) that shrink Prometheus scrape payloads. Dates are the real ones rather than provisional, but they were inferred from the v26.40.1 tag's commit date (2026-09-05T01:54:28Z) plus one day rather than supplied — see the PR description. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release notes for v26.40.1, a three-commit hotfix train with no RC snapshots —
finalis its only snapshot, so this PR carries one commit and the dates set here are the real ones rather than provisional.Please confirm the dates before merging. They were inferred from the
v26.40.1tag's commit date (2026-09-05T01:54:28Z) plus one day, not supplied: Cloud 2026-09-05 / Self-Managed 2026-09-06. The tag was cut at 01:54 UTC on a Saturday, and a hotfix tagged in the small hours of a weekend does not typically reach Cloud the same day, so the real Cloud date may well be later.What this release is. Both entries are metric-cardinality work: #38614 removes the
mz_timestamp_difference_for_strict_serializable_msmetric (which the author declared in an explicit release note) and trims twomz_time_to_first_row_secondsbuckets; #38640 (INC-1252) stops per-cluster series leaking for dropped clusters. The peek-path performance claim in #38614 is deliberately not published — the PR measures the metrics side only and reports no peek-latency number.Needs a decision — overlap with v26.41.0 (#38667). These commits are cherry-picks, so they are also in the
v26.41.0train, whoserc.1draft demoted #38614 to Borderline under the internal-observability rule. This PR departs from that on the evidence that the removed metric is listed on the published Appendix: Metrics page (the shortcode there takes novisibilityfilter, so it lists internal metrics too). If these entries stay here, v26.41.0 should not restate #38614/#38640 — its snapshot directories currently omit both, which is the consistent outcome. If you prefer therc.1treatment, cut these two entries here rather than adding them there. What must not ship is the metric being announced twice.Merge ordering:
## v26.40.1must stay above## v26.40.0. #38667 (v26.41.0) is also open againstmain; whichever of the two merges second needs its section placed relative to the other by hand.Snapshot drafts (with PR links) in mz-skills:
Borderline PRs omitted: final: 1 — review borderline calls