v26.41.2 release notes - #38938
Open
bosconi wants to merge 1 commit into
Open
v26.41.2 release notes#38938bosconi wants to merge 1 commit into
bosconi wants to merge 1 commit into
Conversation
Adds the `## v26.41.2` section to the releases index and the matching operator-compatibility row. This patch train has no RC snapshots, so `final` is its only snapshot and this commit creates the branch. The single published entry is the rustls RUSTSEC-2026-0285 fix; the other four PRs in the increment are CI and test-harness repair, recorded in the snapshot's omitted.md. Dates are inferred from the v26.41.2 tag date and need confirmation from the release owner before merging.
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
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.41.2.This is a patch train with no RC snapshots, so
finalis its only snapshot and this PR carries a single commit. The dates below are inferred from thev26.41.2tag date (2026-09-18T15:57:08Z) rather than supplied — please confirm both with the release owner before merging. In particular the Cloud line is doubtful:v26.42.0released to Self-Managed on the same calendar day, sov26.41.2may be a Self-Managed-only patch for operators pinned to thev26.41line, in which case the Cloud line should be deleted rather than re-dated.Two other things a reviewer should decide deliberately:
rustls) was cut by a human editor from## v26.42.0in 6f71a2f on v26.42.0 release notes #38761. It is published here anyway because it is the entire substance of this release — cut it and## v26.41.2is a version heading with no content — and because a patch release on an older line is taken precisely by operators tracking advisories against that line. If you do cut it, cut the bullet and let the section carry only the dates.## v26.41.2sits below## v26.42.0and above## v26.41.0, matching version order.docs/v26.41.1-release-notes(v26.41.1 release notes #38909) is also open and its section belongs directly below this one, so whichever merges last needs its section placed by hand. The operator-compatibility row follows the same version ordering and therefore sits belowv26.42even though its release date is a day later.Snapshot drafts (with PR links) in mz-skills:
Borderline PRs omitted: final: 1 — omitted.md#borderline