Whether from a particular release to another or from an arbitrary point in latest to the latest latest, if a change between commits x and y cannot be applied by the built-in updater, instead requiring the container be rebuilt from a new image, will the new release notes system identify that and make note of the need for a rebuild?
Separately, will the built-in updater prevent the update, prompting for a rebuild?
My loose understanding of the built-in updater is that after updating Docker_manager, it will block updating Discourse if a rebuild is required. I haven’t seen this formalised though and anecdotally it hasn’t seemed completely reliable.
Specifically, sometimes navigating from the completed Docker_manager update to the Versions page will have the Discourse update available to start, then only after refreshing the page will it be blocked. [I will note that the last time I saw that happen was quite a long time ago though, maybe it was fixed.]