Hi @imanickam 🙂 Thanks for your encouraging words. I think you identify two issues:
a) an issue caused by rc5
b) ability to choose specific MySQL versions
Sorry to hear rc5 broke your sites! What was the exact error?
To get your stacks up and running as easily as possible I would suggest rebuilding them (right-click the stack name in the left-hand stack listing and choose "Rebuild..."). That will upgrade your stack's installed services. However, as you discovered, a consequence is that it will upgrade MySQL 8.0 to 8.1.
I will need to see if I can replicate your issue with rc5, so any other info you can add will be helpful.
MySQL is by far the heaviest service we include within the Indigo app bundle (~260 & ~400MB for v5.6 and v8.1 respectively). As such I'd like to avoid shipping more than two versions with Indigo. Long-term it would be awesome to have Indigo download services on-demand, so we could continue offering old versions, but that'll be a long way off. So in the meantime, I've tried to include a pragmatic selection. My thinking with all services is to identify the versions developers typically care about. For example with PHP a developer might know they want v8.2. They won't care if they get 8.2.4 or if it's silently upgraded to 8.2.5. They just want 8.2. With MySQL, it's a little more difficult — on one hand my feeling is that a majority of developers will want the current release of MySQL 8.x, and not really know or care if it's 8.0.x or 8.1.x. On the other hand, 8.1 is a new release, not a minor release of 8.0, and as such not a usual candidate for a silent upgrade.
All that said, in the end, given the constraints we're working within I went with including only 5.6.x and 8.x. That means when a new v5.6 is released, Indigo will bundle it, and when a new v8 is released, whether 8.1 or 8.2 or whatever, Indigo will bundle that.
I'd value everyone's feedback on this strategy.