Do version upgrades happen automatically? I though...
# community-help
a
Do version upgrades happen automatically? I thought they didn't, but we got upgraded to
v29.0.rc27
from
v28
(iirc) un-prompted. We're on Typesense Cloud with 3 nodes
a
Hi Alan, I will be reaching out in your DM for security and privacy reasons since is related to your team!
🙏 1
Summarizing our conversation for other users who might have similar questions in the future: We do not upgrade Typesense Versions automatically under normal course of operations. However, if we identify that a cluster is running into an issue that we've specifically fixed in a more recent RC build and if that will help improve cluster stability, only then do we upgrade Typesense versions and send an email notification out.
s
@Alan Martini It’s good as long as the new RC build doesn’t introduce any regression issues — like what happened to us with RC26, even though we upgraded manually. If the auto-upgrade breaks any existing customer functionality, it won’t be a good experience for the client. So I believe auto upgrading to Stable release is a better idea instead of RC.
k
Both RC and GA releases can have bugs, as with all evolving software. The RC builds exist for us to keep moving forward so that we can patch such issues. We only force an RC upgrade when the act of not doing so causes significant cluster issues. So we always weigh the risk.
s
@Kishore Nallan Absolutely — the community understands well that no software is ever completely bug-free, which is why engineering practices like RC and GA exist — to mitigate risk and reduce the probability of issues. That said, forcing an RC upgrade — especially when not upgrading causes more harm — is understandable. But in such cases, it’s important to also consider the impact on the client side, particularly when SLAs are in place. So, moving forward, a bit more caution and alignment would help — whether through client consent or at least a clear and timely communication before such actions are taken.