Skip to content

v26.44.1 release notes - #39417

Closed
bosconi wants to merge 1 commit into
mainfrom
docs/v26.44.1-release-notes
Closed

bosconi wants to merge 1 commit into
mainfrom
docs/v26.44.1-release-notes

Conversation

@bosconi

@bosconi bosconi commented Sep 30, 2026

Copy link
Copy Markdown
Member

This train has no RC snapshots, so final is its only snapshot and carries the real release dates (Cloud 2026-09-30, Self-Managed 2026-10-01) rather than provisional estimates.

Snapshot drafts (with PR links) in mz-skills:

Borderline PRs omitted: final: 0 — review borderline calls

Notes for the reviewer:

  • The section anchor is {#v26.44.1-improvements} (full three-component version), because {#v26.44-improvements} is already taken by v26.44.0's section. This matches the existing patch-release anchors {#v26.30.1-improvements} and {#v26.40.2-bug-fixes}.
  • v26.44.0 release notes #39138 (v26.44.0 release notes) is still open, so _index.md on main begins at ## v26.43.0. Whichever of v26.44.0 release notes #39138 and this PR merges second will need a rebase to land ## v26.44.1 above ## v26.44.0.
  • The one published entry rests on the PR's own measurements rather than an author release-note declaration, and deliberately states the memory saving as a ratio rather than the PR's absolute per-connection byte figures, which its author disclaims as non-transferable to production. Reasoning, the full measurement table, and the internal-TLS deployment precondition that scopes the improvement are in the review-notes appendix of the linked draft.

Adds the v26.44.1 section to doc/user/content/releases/_index.md and the
corresponding row to the Self-Managed operator compatibility table.

This patch train has no RC snapshots, so `final` is its only snapshot and
carries the real release dates (Cloud 2026-09-30, Self-Managed 2026-10-01)
rather than provisional estimates.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@bosconi
bosconi requested a review from a team as a code owner September 30, 2026 19:01
maheshwarip added a commit that referenced this pull request Sep 30, 2026
v26.44.0 did not ship, so the v26.44 train releases as v26.44.1 with
the same dates. Rename the section, its anchors, and the operator
compatibility row to v26.44.1, set `patch: 1` on the release page, and
fold in the balancerd TLS connector memory improvement from #39417.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@maheshwarip

Copy link
Copy Markdown
Contributor

changes incorporated into #39138

maheshwarip added a commit that referenced this pull request Oct 1, 2026
v26.44.0 did not ship, so the v26.44 train releases as v26.44.1 with
the same dates. Rename the section, its anchors, and the operator
compatibility row to v26.44.1, set `patch: 1` on the release page, and
fold in the balancerd TLS connector memory improvement from #39417.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
maheshwarip added a commit that referenced this pull request Oct 2, 2026
v26.44.0 did not ship, so the v26.44 train releases as v26.44.1 with
the same dates. Rename the section, its anchors, and the operator
compatibility row to v26.44.1, set `patch: 1` on the release page, and
fold in the balancerd TLS connector memory improvement from #39417.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
maheshwarip added a commit that referenced this pull request Oct 2, 2026
v26.44.0 did not ship, so the v26.44 train releases as v26.44.1 with
the same dates. Rename the section, its anchors, and the operator
compatibility row to v26.44.1, set `patch: 1` on the release page, and
fold in the balancerd TLS connector memory improvement from #39417.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants