Skip to content

Clarify upgrade process in Cloud overview page #5152

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
morsapaes merged 1 commit into from
Jan 6, 2026
Merged

Clarify upgrade process in Cloud overview page #5152

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/about-us/cloud.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,8 +47,8 @@

## What version of ClickHouse does ClickHouse Cloud use? {#what-version-of-clickhouse-does-clickhouse-cloud-use}

Clickhouse Cloud continuously upgrades your service to a newer version. After publishing a core database version in the open source, we do additional validation in our cloud staging environment, which typically takes 6-8 weeks before rolling out to production. The rollout is phased out by cloud service provider, service type, and region.
Clickhouse Cloud periodically upgrades your service to newer versions that include fixes, new features and performance improvements. After publishing a core database version in the open source, we do additional validation in our cloud staging environment, which typically takes 6-8 weeks before rolling out to production. The rollout is phased out by cloud service provider, service type, and region.

We offer a "Fast" Release Channel for subscribing to updates ahead of the regular release schedule. For more details, see ["Fast Release Channel"](/manage/updates#fast-release-channel-early-upgrades).
You can specify the upgrade schedule for your ClickHouse Cloud service by subscribing to a specific release channel. For example, we offer a ["Fast" Release Channel](/manage/updates#fast-release-channel-early-upgrades) for subscribing to updates ahead of the regular release schedule, as well as a ["Slow" Release Channel](/manage/updates#slow-release-channel-deferred-upgrades) and other more granular scheduling options for deferred upgrades.

Check notice on line 52 in docs/about-us/cloud.md

View workflow job for this annotation

GitHub Actions / vale

ClickHouse.Wordy 

Suggestion: Use 'and' instead of 'as well as'.

If you rely on functionality in the earlier version, you can, in some cases, revert to the previous behavior using your service's compatibility setting.
For an overview of ClickHouse Cloud's upgrade process, including backwards compatibility guarantees, see the reference documentation for [Upgrades](/manage/updates).
Loading