v26.41.1 release notes - #38909
Open
bosconi wants to merge 1 commit into
Open
v26.41.1 release notes#38909bosconi wants to merge 1 commit into
bosconi wants to merge 1 commit into
Conversation
Add the `## v26.41.1` section to the releases index and a `v26.41.1` row to the Self-Managed operator compatibility table. Dates are the real ones for this train: Cloud 2026-09-17, Self-Managed 2026-09-18.
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.
Dates in RC snapshots are provisional until the release ships. One commit is added per snapshot; the final snapshot sets the real dates.
v26.41.1is a single-snapshot patch train — it has no RCs, so this PR carries one commit and the dates are real, not provisional.Snapshot drafts (with PR links) in mz-skills:
Borderline PRs omitted: final: 0 — omitted.md#borderline
Two things for the reviewer
v26.41.1tag's commit date (2026-09-17T04:26:52Z) plus one day, not supplied by the release owner.visibility: internal, but the published Appendix: Metrics page renders the catalog unfiltered, so all 12 names are documented surface. It is also not inv26.42.0— it missed that branch by ~13 hours and was cherry-picked ontov26.41instead — so an operator loses these series atv26.41.1, gets them back atv26.42.0, and loses them again atv26.43.0. Options: add a forward-looking line tov26.42.0's notes (v26.42.0 release notes #38761 is still open); publish as-is and accept the churn; or cut the bullet here and publish once atv26.43.0. Full evidence and the contrary argument are in the review-notes appendix of the linked draft.