Repository navigation
v26.46.0 release notes - #39690
Merged
Merged
v26.46.0 release notes#39690
Conversation
Adds the `## v26.46.0` section to `doc/user/content/releases/_index.md` and the operator compatibility row for v26.46, from the rc.1 snapshot. Dates are provisional (Cloud 2026-10-15, Self-Managed 2026-10-16) and are set for real by the final snapshot.
Moves the materialize-sink-id header entry out of Improvements into a private-preview section, matching how SCIM role mapping was announced in v26.34, and links to the CREATE SINK Headers docs. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Brings in the v26.45.0/v26.45.1 consolidation and the rest of main, which this branch was 89 commits behind. Conflicts in doc/user/content/releases/_index.md and the operator-compatibility YAML were both the top-of-list insertion point: resolved by keeping this branch's v26.46.0 section and row above main's consolidated v26.45.1 ones. Section order is now v26.46.0, v26.45.1, v26.44.1.
The final snapshot of this train publishes no new entries: comparing v26.46.0-rc.1...v26.46.0 is ahead_by 1 and that commit is the version bump, so nothing was cherry-picked onto the release branch after rc.1. The five agent-skills PRs in the window are four automated mz-docs regenerations plus one prose clarification, all omitted. The real dates - Cloud 2026-10-15, Self-Managed 2026-10-16 - are identical to the provisional pair rc.1 estimated, so the two date lines in _index.md and the Release date in the operator-compatibility YAML already carry them and need no edit. This commit records the snapshot as applied. One item for the release owner: Metric Sinks, the release's headline feature, still has no user-facing documentation at the final tag - doc/user has no page for CREATE METRIC SINK, DROP METRIC SINK, or SHOW METRIC SINKS. Either a docs page lands with the release, or the section is held for the release that ships its documentation.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Removed sections on Metric Sinks and Kafka sink message attribution from the release notes for version 26.46.0.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Cut the Console account-pages entry (Cloud-only, live in Cloud before the release) and the replica-scoped override fix (internal flags only). Drop "by default" from read-then-write (the flag was removed), narrow the network policy entry to create/alter, note that Kafka sources on private brokers stall on reconnect, and trim internal detail elsewhere. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Advises Self-Managed deployments with upsert sources to hold off on upgrading to v26.46.0 because of a potential performance regression, following the advisory format used for the v26.30.1 MySQL YEAR change. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
maheshwarip
enabled auto-merge (squash)
October 16, 2026 17:51
maheshwarip
approved these changes
Oct 16, 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
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 the v26.46.0 train. Dates in RC snapshots are provisional until the release ships. One commit is added per snapshot; the final snapshot sets the real dates.
rc.1.finaladds no entries.v26.46.0-rc.1...v26.46.0isahead_by: 1and that commit is the version bump, so nothing was cherry-picked onto the release branch afterrc.1. The five agent-skills PRs in the window are four automatedmz-docsregenerations plus one prose clarification, all omitted.rc.1estimated, so no date line changed in this run. Thev26.46.0tag was cut 2026-10-14 (Wednesday); the first Thursday on or after it is 2026-10-15, Self-Managed the day after.v26.46, release date2026-10-16.mainin this run (it was 89 commits behind). The merge conflict was the top-of-list insertion point in both files; resolved keepingv26.46.0abovemain's consolidatedv26.45.1. Section order is nowv26.46.0,v26.45.1,v26.44.1.enable_metric_sinkistrueinsrc/sql/src/session/vars/definitions.rs, re-verified atv26.46.0, so availability is established — butdoc/userstill has no page forCREATE METRIC SINK,DROP METRIC SINK, orSHOW METRIC SINKS. Either a docs page lands with the release, or the Metric Sinks section is held for the release that ships its documentation; publishing the heading as-is sends readers to a 404. (Also stale, harmlessly:doc/developer/generated/sql/session/vars/definitions.mdstill describes the default asfalse.)persist_part_decode_batch_rowsis unset at the tag. If the batch size is being turned on for this release, this is a strong Improvement — the PR measures an OOM-killed hydration becoming 303 s on TPC-H SF100lineitem.CDC_CLEANUP_CHANGE_TABLE, which defaults off. Publish if the flag is being enabled.persist_shard_metricsand friends, but production keepsboth, so no scrape shrinks in this release. Should self-managed operators be told the knob exists before their scrape is the one that breaks at ~390k series?UNIQUEconstraint fix and its revert (#39598, #39660, both omitted): net zero shipped behavior, but the planner defect is still open and the near-miss was anenvironmentdboot panic after upgrade, not a cosmetic one.mainin this window. If it warrants a note, that note belongs on## v26.45.1(#39661), not here.Kafka sink message attribution (#39566, #39590): confirm the private-preview wording.Settled on this branch — the entry is its own section using the{{< private-preview />}}shortcode and linkingCREATE SINK: Headers.Snapshot drafts (with PR links) in mz-skills:
Borderline PRs omitted: rc.1: 10 — omitted.md#borderline, final: 1 — omitted.md#borderline
🤖 Generated with Claude Code