Skip to content

Update upgrades.md #4148

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
merged 3 commits into from
Jul 27, 2025
+4 −0
Merged

Update upgrades.md #4148

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
af1e7d9
Update upgrades.md
krithika-ch Jul 22, 2025
be3f2b9
Update upgrades.md
Blargian Jul 22, 2025
101916a
Update docs/cloud/manage/upgrades.md
Blargian Jul 25, 2025
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
4 changes: 4 additions & 0 deletions docs/cloud/manage/upgrades.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -97,6 +97,10 @@ Specifically, services will:
- Receive ClickHouse releases ~ 2 weeks after the regular release
- Be meant for customers that want additional time to test ClickHouse releases on their non-production environments before the production upgrade. Non-production environments can either get upgrades on the Fast or the Regular release channel for testing and validation.

:::note
You can change release channels at any time. However, in certain cases, the change will only apply to future releases. For example, if your service is already on the Fast release channel and has received the upgrade, switching to a regular or slow release channel will not downgrade your service to a previous version. It will follow the channel specific release schedule for upcoming updates.
:::

## Scheduled upgrades {#scheduled-upgrades}

<EnterprisePlanFeatureBadge feature="Scheduled upgrades" linking_verb_are="true"/>
Expand Down