Document updating process of Zitadel
Hey everyone,
I just had a chat with @Raccine for evaluating the onboarding process of Zitadel. I remembered that I could find any mention about some conventions regarding migrations and updating Zitadel.
Specifically, when upgrading from X.Y.Z to X.Y+W.Z+K, what’s the recommended approach?
- Can I always jump straight to the target version?
- Do I need to go through all minor versions in order?
- If moving through minors, should I always pick the latest patch of each?
For example, say I’m on 7.2.3 and want to get to 7.5.1—should I:
- Go straight to 7.5.1?
- Upgrade step by step through minor versions, but always take the highest patch (e.g., 7.2.3 → 7.3.x → 7.4.y → 7.5.1 - with x and y set to the latest patch for that Minor)?
- Do something else entirely?
Would be great to know if this is already written down somewhere or if it makes sense to add it to the docs. Thanks!
I just had a chat with @Raccine for evaluating the onboarding process of Zitadel. I remembered that I could find any mention about some conventions regarding migrations and updating Zitadel.
Specifically, when upgrading from X.Y.Z to X.Y+W.Z+K, what’s the recommended approach?
- Can I always jump straight to the target version?
- Do I need to go through all minor versions in order?
- If moving through minors, should I always pick the latest patch of each?
For example, say I’m on 7.2.3 and want to get to 7.5.1—should I:
- Go straight to 7.5.1?
- Upgrade step by step through minor versions, but always take the highest patch (e.g., 7.2.3 → 7.3.x → 7.4.y → 7.5.1 - with x and y set to the latest patch for that Minor)?
- Do something else entirely?
Would be great to know if this is already written down somewhere or if it makes sense to add it to the docs. Thanks!
