v26.40.2 release notes - #38707
Merged
Merged
Conversation
Adds the `## v26.40.2` section to the releases page and the matching Self-Managed operator-compatibility row. This train has no RC snapshots; `final` is its only snapshot, so this commit carries the whole release note with the real release dates.
maheshwarip
approved these changes
Sep 8, 2026
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
3 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.2, a patch release. One commit is added per snapshot; this train has no RC snapshots, so the singlefinalcommit carries the whole note with the real release dates.Snapshot drafts (with PR links) in mz-skills:
Borderline PRs omitted: final: 1 — omitted.md#borderline
Two things for the reviewer
v26.40.2tag's commit date (2026-09-07T19:27:35Z) plus one day. The tag was cut Monday evening UTC, so a next-day Cloud rollout is at least as likely as a same-day one. Please confirm both dates before merging.v26.41.0-rc.4. Both trains took the same tworelease-blockercherry-picks on 2026-09-07, so#38677is drafted as a Bug Fix in both v26.41.0 release notes #38667 and here.v26.40.2ships it to Cloud first, so if both merge as drafted the same fix is announced in consecutive releases.v26.40.1(v26.40.1 release notes #38675) raised the same question and answered it the other way. Worth settling once for both patches.Merge ordering:
## v26.40.2must sit above## v26.40.1(#38675), which must sit above## v26.40.0. #38675, #38667, and #38365 (v26.38.1) are all still open, so whichever merges last will need its section placed by hand relative to the others.