Repository navigation
v26.45.1 release notes - #39661
Merged
Merged
v26.45.1 release notes#39661
Conversation
Adds the v26.45.1 section to the releases index and the corresponding Self-Managed operator compatibility row. The release contains two commits: a cherry-picked per-subsystem chunk spill gate change (#39659), whose author declares "None. No user-visible change.", and the version bump automation. The section therefore carries dates only. See the mz-skills snapshot draft for the omit reasoning. Dates are the real release dates, inferred from the v26.45.1 tag.
…g to v26.45.1 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…s, trim alerting Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
v26.45.0 did not ship, so the v26.45 train releases as v26.45.1, as v26.44 did. Move the v26.45.0 Improvements, Agent Skills, and Bug Fixes entries from #39477 into the v26.45.1 section verbatim, with anchors renamed to {#v26.45.1-...}. Dates, the operator compatibility row, and v26.45.md were already correct for v26.45.1. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
The train shipped to Cloud on Thursday 2026-10-08 and to Self-Managed on 2026-10-09. The generated dates were the v26.45.0/v26.45.1 tag date (Wednesday 2026-10-07), one day early. Fix the section and the operator compatibility row. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
val-materialize
pushed a commit
that referenced
this pull request
Oct 8, 2026
Seven sections in the release notes give release dates one day early. Release notes use the day of the **US** rollout (Thursday) as the Cloud date and the day the **Helm chart is published** (Friday) as the Self-Managed date. From v26.35.0 on, the generated notes used the final tag's date instead, and that tag is cut on Wednesday. The generator is fixed going forward by MaterializeInc/mz-skills#301. | Section | Cloud | Self-Managed | Evidence | |---|---|---|---| | v26.44.1 | 09-30 → **10-01** | 10-01 → **10-02** | US rollout 10-01; Helm 10-02 | | v26.43.0 | 09-23 → **09-24** | 09-24 → **09-25** | US rollout 09-24; Helm 09-25 | | v26.40.0 | 09-02 → **09-03** | 09-03 → **09-04** | US rollout 09-03; Helm 09-04 | | v26.39.0 | 08-26 → **08-27** | 08-27 → **08-28** | US rollout 08-27; Helm 08-28 | | v26.38.2 | 08-19 → **08-20** | 08-25 (unchanged) | US rollout of v26.38.0 08-20 | | v26.37.0 | 08-12 → **08-13** | 08-13 → **08-14** | US rollout 08-13; Helm 08-14 | | v26.35.0 | 07-29 → **07-30** | 07-30 → **07-31** | US rollout 07-30; Helm 07-31 | The operator compatibility rows for v26.44.1, v26.43, v26.40, v26.39, v26.37 and v26.35 move to the same Self-Managed dates. The US rollout dates come from the `upgrade-production-us` runs in #release. The Helm dates come from the chart's `created` timestamps in `index.yaml` on `gh-pages`. **Left alone; may be worth a look:** - v26.40.2 says Cloud 09-07 / Self-Managed 09-08, but its Helm chart was published 09-10. - v26.41.0's Helm chart is stamped 09-13 04:08 UTC, which is a day after the Self-Managed date of 09-11. - The `v26.38` compatibility row (08-20) has no published v26.38.0 chart. **Merge order:** this PR and #39661 (v26.45.1) both edit the lines right below the top of `_index.md` and the compatibility YAML. Whichever merges second will need a trivial rebase. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Cut entries for changes customers could not hit (MariaDB parsec abort, stale OpenSSL error, Corrupt footer on rustfs) and the group-sync notice change, which is Cloud-only behind a flag that defaults off. Narrow the interval aggregate, orphaned replica, Console utilization, alerting and mz-demo-data entries to what the source PRs support. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Trim each entry to one or two sentences, and drop the mz-debug-freshness, hedged-read and orphaned-replica entries. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
val-materialize
approved these changes
Oct 8, 2026
Contributor
|
Approving after a correctness pass against the source PRs at the v26.45.1 tag. Cut as unverifiable or not customer-facing: Quieter logins (Cloud-only, oidc_group_role_sync_enabled defaults off), MariaDB parsec abort (bug never released), stale OpenSSL error (CI-only; ccsr no longer uses OpenSSL), Corrupt footer (no supported store affected). Also dropped for length: mz-debug-freshness, hedged reads, orphaned replicas. Remaining entries trimmed to verified claims. Follow-up for the TLS SME: the certificate entries don’t yet mention that MaterializeInc/materialize#39351 applies the same SAN rule to custom S3/AWS endpoints, or that in-cluster API server certs need an IP SAN, and may belong in a breaking-changes callout. |
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 the v26.45 train, published as v26.45.1. v26.45.0 did not ship, so (as with v26.44) its notes are folded in here and #39477 is closed unmerged.
{#v26.45.1-…}.v26.45.1.v26.45.md(patch: 1, norc) is already onmain.oidc_group_role_sync_enableddefaults tofalseat the tag. Is it on in Cloud? If not, cut the "Quieter logins" bullet.enable_upsert_paged_spillon in production? A draft bullet is in omitted.md.EXPLAIN ANALYZE ... CPU: agent-skills#90 says it overstates joins, reductions, and TopK by 1.5x–3x before v26.46. Not published. Is that a known issue?enable_metric_sinkisfalse. sql: treat '' as the empty list for identifier-list vars #39337 fixes a panic any superuser can reach, so consider publishing it regardless.Snapshot drafts in mz-skills: v26.45.0 (rc.1–rc.4, final), v26.45.1.
🤖 Generated with Claude Code