Update notification for pre-release version?

[Jarod]

Hey, I just got that update notification

I don't really want to install a pre-release version, but I still got that as an update notification. How can I disable getting notifications for pre-release versions and will I get another, when it's not in pre-release anymore?

[girish]

mm, I think you get that notification when you click the 'Update' button, no? Or did you get some email about this or something in the notification view ? You don't need to worry, it won't automatically update to unstable releases.

[giofonseca]

Hey @girish could you please elaborate a bit more on what does it mean, the first change: ami: "disable Route53"? We are using AWS Route53 to manage our DNS, and I want to be sure that if I upgrade to Cloudron v8.1, we will be able to still using that feature properly.

Thanks in advance!

[Jarod]

@girish I got it as a notification in the web interface

[nebulon]

To clarify a bit, if you check for updates manually, you will also see the update option to releases which are about to be rolled out for automatic updates. We usually do this over at least a week to not update all Cloudrons out that all at once. This is just a safety precaution in case we have an unnoticed regression. Currently we are in the phase of rolling out Cloudron v8 so if you are manually checking for updates, the Cloudron will show that. If you see the pre-release hint, this just means that your Cloudron is not yet part of the blocks which are marked for auto-updates. This is simply done based on the alphabetic ordering of the dashboard domain for no real reason, other than just having rather evenly distributed blocks.

Initially we didn't have this behavior, however some eager users wanted to try new things immediately or some also required specific fixes early of the newer releases. So this was just a pragmatic fix, but maybe we can adjust the wording to make that a big more clear.

[girish]

@Jarod In the AWS Marketplace Image (AMI) , route53 is disabled in the setup screen. It is apparently against Marketplace policy to take route53 API credentials (a member of their team had reached out to us and notified us about this). So, if you use the AMI, then the setup screen will not show route53 as an option anymore.