Docs: publish Cloud database release changelog for 26.6 - #116789
Draft
dhtclk wants to merge 21 commits into
Draft
Conversation
Publish the curated public changes from Release Radar and add the release to the Cloud changelog navigation. Context: https://linear.app/clickhouse/issue/DOC-1014/publish-cloud-database-release-changelog-for-266 Source: https://release-radar.tail983ac.ts.net/changelog/26.6
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Contributor
|
Workflow [PR], commit [2115c3d] Summary: ✅ AI ReviewSummaryThis PR adds the public Cloud Findings💡 Nits
Final VerdictNeeds minor docs cleanup before merge: the content itself looks substantially improved, but the remaining subsection labels should match the bullets they contain. |
Blargian
requested changes
Aug 28, 2026
Blargian
left a comment
Member
There was a problem hiding this comment.
Lot more pruning required. Let's run it through Claude again and remove all of the irrelevant entries.
Blargian
approved these changes
Aug 28, 2026
| ### ClickHouse Keeper {#clickhouse-keeper-improvements} | ||
|
|
||
| * Various changes to Keeper that make it around 2x faster overall (better batching, pipelining messages to leader, pipelining log appends). [#101757](https://github.com/ClickHouse/ClickHouse/pull/101757) ([al13n321](https://github.com/al13n321)). | ||
| * `OPTIMIZE TABLE ... ON CLUSTER` and other DDL no longer hang when the target table has `table_readonly = 1`. The setting now throws a new dedicated error code `TABLE_IS_PERMANENTLY_READ_ONLY`, which `DDLWorker` treats as non-retriable (distinct from the transient `TABLE_IS_READ_ONLY` that arises during temporary `ReplicatedMergeTree` ZooKeeper disconnects). The `table_readonly` setting is also now explicitly rejected for `ReplicatedMergeTree`, both at creation and via `ALTER MODIFY SETTING`. [#105109](https://github.com/ClickHouse/ClickHouse/pull/105109) ([alexey-milovidov](https://github.com/alexey-milovidov)). |
Contributor
There was a problem hiding this comment.
This bullet's primary surface is table_readonly / DDLWorker behavior, not ClickHouse Keeper. Grouping #105109 under the Keeper subsection makes it hard for readers scanning by area to find the follow-up to table_readonly, and it reads oddly next to the surrounding Keeper-only bullets (system.keeper_*, coordination_settings, snapshot memory). Please move this entry into a storage/settings or generic improvements subsection.
| * Fix credential leaks in `SHOW CREATE`, `system.query_log`, server logs and `EXPLAIN` output. Every `S3` locator form now masks `session_token` and Google ADC secrets, `extra_credentials`/`headers` values at any argument position, duplicated or expression secret keys, invalid positional forms (fail closed), and credentials embedded in S3 URLs; this covers the explicit-url and named-collection `s3`/`s3Cluster` table functions, the S3-backed table engines (`S3`, `GCS`, the data-lake engines, `S3Queue`), the `S3` database engine, `BACKUP ... TO S3` and the `Backup` database engine. In addition, secret arguments of `encrypt`/`decrypt`/HMAC that are built by an expression (including ones inlined from a SQL UDF) are now hidden in projection names, `EXPLAIN QUERY TREE` and `EXPLAIN actions`. [#109768](https://github.com/ClickHouse/ClickHouse/pull/109768) ([Algunenano](https://github.com/Algunenano)). | ||
| * Fix `S3Queue`/`AzureQueue` ordered mode with persistent processing nodes: bucket locks are now refreshed during streaming, so that the TTL cleanup (`persistent_processing_node_ttl_seconds`) does not remove locks of a live processor. If lock ownership is nevertheless lost, it is detected and reported (a logical error and the `ObjectStorageQueueBucketLockLostOwnership` profile event), and streaming recovers with a fresh file iterator. [#110292](https://github.com/ClickHouse/ClickHouse/pull/110292) ([kssenii](https://github.com/kssenii)). | ||
|
|
||
| ### Security and access control fixes {#security-and-access-control-fixes} |
Contributor
There was a problem hiding this comment.
This section title is too narrow for several of the bullets it currently contains. #103322, #104917, #105068, and #106459 are ordinary query, data-lake, parser, and named-collection changes rather than security or access-control fixes, so readers scanning the changelog for actual security work will get a misleading picture of 26.6. Please either split the non-security items into a neutral bug-fix subsection or rename this section to something broader.
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.
Publishes the ClickHouse Cloud database release changelog for version 26.6. The page follows the existing Cloud changelog structure, adds it to the release-note navigation and index, and updates the legacy redirect.
The entries were curated from Release Radar; private repository changes were omitted, consistent with the previous public changelogs. The page was validated with a local Mintlify preview and an MDX parse check.
Task: DOC-1014
Changelog category (leave one):
Changelog entry (a user-readable short description of the changes that goes into CHANGELOG.md):
Not applicable.
Workflow [PR]
Sync PR [sync-upstream/pr/116789]