Update upgrades.md #4148
Merged
Update upgrades.md #4148
Conversation
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
Added a note :::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 sepecific release schedule for upcoming updates. :::
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
3 Skipped Deployments
|
Crazybus
reviewed
Jul 23, 2025
docs/cloud/manage/upgrades.md
Outdated
| @@ -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. | |||
There was a problem hiding this comment.
However, in certain cases, the change will only apply to future releases.
What are the cases? Maybe instead of listing one case we could be explicit and explain both cases.
- Moving to a faster channel will immediately upgrade your service.
- Moving to a slower channel will not downgrade your service and keep you on your current version until a newer one is available in that channel.
Co-authored-by: Michael Russell <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Added a note
:::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 sepecific release schedule for upcoming updates. :::
Summary
Checklist