Upgrade from 3.5.0 -> 3.5.1 required rebuild?

[rahim123]

I guess this is sort of a continuation of:

PSA: Stable 3.3.3 -> 3.4.0 upgrade via GUI failed, had to rebuild via command line

Just a heads-up for self-hosted stable branch users. For me the upgrade via the GUI failed, I’m not sure if this would happen to everyone, as I saw some errors about unicorn processes, which tends to be a random issue in my experience. But at any rate that left my forum in a state where it claimed to be up-to-date in /admin/update while still being stuck on the old version. So I had to SSH into the server and /var/discourse/launcher rebuild app two times, the first time it just upgrades Postgre…

I updated from 3.5.0 to 3.5.1 (stable channel) via the upgrade GUI (both the Docker manager and Discourse) and everything seemed to go well. But once it finished I checked the upgrade GUI again (force reload of the page), and it said something about how it wasn’t running the latest image and would require a launcher rebuild for the next update. So I did that and everything again worked fine.

This isn’t really a problem per se, as I have a fairly good handle on managing Discourse via the command line. But it seemed strange that this would be required for a X.y.z minor release from the stable branch, and after successfully completing the GUI upgrade. I don’t think there were any Postgres updates for this minor point release? On this occasion I had time to SSH in and do the rebuild, but it would have been a much bigger issue if I was traveling or otherwise didn’t have access to a terminal. Just wondering if there’s a rhyme or reason to all this. Thanks!