From 2f5714bf7ac2677c4bbebafd1dfff0d1ae3e741d Mon Sep 17 00:00:00 2001 From: Claude Date: Mon, 24 Aug 2026 21:39:21 +0000 Subject: [PATCH 1/4] v26.38.2 release notes (final) Adds the v26.38.2 section to the releases index and a row to the self-managed operator compatibility table. Dates are the real release dates for this train: Cloud 2026-08-24, Self-Managed 2026-08-25. This train has no RC snapshots, so `final` is its only snapshot. --- doc/user/content/releases/_index.md | 10 ++++++++++ .../self_managed_operator_compatibility.yml | 5 +++++ 2 files changed, 15 insertions(+) diff --git a/doc/user/content/releases/_index.md b/doc/user/content/releases/_index.md index a21c7ea600e2c..58385d793ca79 100644 --- a/doc/user/content/releases/_index.md +++ b/doc/user/content/releases/_index.md @@ -19,6 +19,16 @@ Starting with the v26.1.0 release, Materialize releases on a weekly schedule for both Cloud and Self-Managed. See [Release schedule](/releases/schedule) for details. {{}} +## v26.38.2 +*Released to Materialize Cloud: 2026-08-24*
+*Released to Materialize Self-Managed: 2026-08-25*
+ +### Agent Skills {#v26.38.2-agent-skills} +- **materialize-debug-freshness**: New skill that diagnoses why an object is behind wall-clock time, sweeping source and sink status, attributing lag hop by hop through `mz_materialization_lag`, and — once hydration is confirmed — ranking the dataflows on a replica and then that dataflow's operators back to the query clause responsible. + +### Bug Fixes {#v26.38.2-bug-fixes} +- Fixed slow catalog queries immediately after a zero-downtime upgrade that migrated builtin materialized views: the migrated views and everything downstream of them used to hydrate all at once at cut-over, spiking CPU on `mz_catalog_server`, and now hydrate before cut-over instead. + ## v26.38.0 *Released to Materialize Cloud: 2026-08-19*
diff --git a/doc/user/data/self_managed/self_managed_operator_compatibility.yml b/doc/user/data/self_managed/self_managed_operator_compatibility.yml index 5f20b9c81180f..d9b91ab20e01b 100644 --- a/doc/user/data/self_managed/self_managed_operator_compatibility.yml +++ b/doc/user/data/self_managed/self_managed_operator_compatibility.yml @@ -5,6 +5,11 @@ columns: - column: Release date - column: Notes rows: + - Materialize Operator: v26.38.2 + orchestratord version: v26.38.2 + environmentd version: v26.38.2 + Release date: "2026-08-25" + Notes: "See [v26.38.2 release notes](/releases/#v26382)" - Materialize Operator: v26.38 orchestratord version: v26.38 environmentd version: v26.38 From 861c1467b5d3cecebebcb14ad996820e626d9612 Mon Sep 17 00:00:00 2001 From: Jon Currey Date: Tue, 25 Aug 2026 16:02:21 +0100 Subject: [PATCH 2/4] docs: drop the Cloud release line from v26.38.2 v26.38.2 is not being released to Materialize Cloud, so the section keeps only its Self-Managed line. The compatibility table row is unaffected: it records the Self-Managed operator release, which is still happening. Co-Authored-By: Claude Opus 5 --- doc/user/content/releases/_index.md | 1 - 1 file changed, 1 deletion(-) diff --git a/doc/user/content/releases/_index.md b/doc/user/content/releases/_index.md index 58385d793ca79..59fc5d69f245a 100644 --- a/doc/user/content/releases/_index.md +++ b/doc/user/content/releases/_index.md @@ -20,7 +20,6 @@ both Cloud and Self-Managed. See [Release schedule](/releases/schedule) for deta {{}} ## v26.38.2 -*Released to Materialize Cloud: 2026-08-24*
*Released to Materialize Self-Managed: 2026-08-25*
### Agent Skills {#v26.38.2-agent-skills} From 1dbfba5b4bf4aaea2d827726270effaa6d54a243 Mon Sep 17 00:00:00 2001 From: Pranshu Maheshwari Date: Tue, 25 Aug 2026 11:14:02 -0400 Subject: [PATCH 3/4] Update _index.md --- doc/user/content/releases/_index.md | 13 ++----------- 1 file changed, 2 insertions(+), 11 deletions(-) diff --git a/doc/user/content/releases/_index.md b/doc/user/content/releases/_index.md index 59fc5d69f245a..c7f8a920b4d56 100644 --- a/doc/user/content/releases/_index.md +++ b/doc/user/content/releases/_index.md @@ -20,16 +20,8 @@ both Cloud and Self-Managed. See [Release schedule](/releases/schedule) for deta {{}} ## v26.38.2 -*Released to Materialize Self-Managed: 2026-08-25*
- -### Agent Skills {#v26.38.2-agent-skills} -- **materialize-debug-freshness**: New skill that diagnoses why an object is behind wall-clock time, sweeping source and sink status, attributing lag hop by hop through `mz_materialization_lag`, and — once hydration is confirmed — ranking the dataflows on a replica and then that dataflow's operators back to the query clause responsible. - -### Bug Fixes {#v26.38.2-bug-fixes} -- Fixed slow catalog queries immediately after a zero-downtime upgrade that migrated builtin materialized views: the migrated views and everything downstream of them used to hydrate all at once at cut-over, spiking CPU on `mz_catalog_server`, and now hydrate before cut-over instead. - -## v26.38.0 *Released to Materialize Cloud: 2026-08-19*
+*Released to Materialize Self-Managed: 2026-08-25*
### Dictionary compression {#v26.38-dictionary-compression} @@ -57,7 +49,7 @@ For more information, see: - [`CREATE CLUSTER`: Dictionary compression](/sql/create-cluster/#dictionary-compression) - [`ALTER CLUSTER`: Dictionary compression](/sql/alter-cluster/#dictionary-compression) - ### Improvements {#v26.38-improvements} - **Notice for single-replica sources on multi-replica clusters**: Materialize now warns when a command leaves a cluster holding more than one replica alongside PostgreSQL, MySQL, or SQL Server sources, which always run on a single replica, since the extra replicas make those sources neither more fault tolerant nor faster to ingest. From 3b6d3ddafbd8d91b43079648f86ce5965ddea15a Mon Sep 17 00:00:00 2001 From: Claude Date: Tue, 25 Aug 2026 16:14:36 +0000 Subject: [PATCH 4/4] docs: point the v26.38 compatibility row at the v26.38.2 anchor The release notes for the v26.38 line now live under a single `## v26.38.2` heading, so the `v26380` anchor the compatibility table linked to no longer exists and `lint-docs` fails with "hash does not exist". Point the row at `#v26382`, the heading that carries those notes. Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_01B7Y4LQEAEfdnUDsttzosR8 --- .../data/self_managed/self_managed_operator_compatibility.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/user/data/self_managed/self_managed_operator_compatibility.yml b/doc/user/data/self_managed/self_managed_operator_compatibility.yml index d9b91ab20e01b..310e6f11ffe83 100644 --- a/doc/user/data/self_managed/self_managed_operator_compatibility.yml +++ b/doc/user/data/self_managed/self_managed_operator_compatibility.yml @@ -14,7 +14,7 @@ rows: orchestratord version: v26.38 environmentd version: v26.38 Release date: "2026-08-20" - Notes: "See [v26.38 release notes](/releases/#v26380)" + Notes: "See [v26.38 release notes](/releases/#v26382)" - Materialize Operator: v26.37 orchestratord version: v26.37 environmentd version: v26.37