Upgrade from 3.5.0 -> 3.5.1 required rebuild?

AI-generated summary

rahim123 reports that after upgrading from Discourse version 3.5.0 to 3.5.1 via the GUI, they were prompted to perform a launcher rebuild to run the latest image. While the process worked fine, they question why this was necessary for a minor release and express concern about the inconvenience if they didn’t have terminal access. They reference a previous post about similar issues with upgrades from versions 3.3.3 to 3.4.0.

I guess this is sort of a continuation of:

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!