The currently followed approach here is not going to work. The source of truth can never be the live GitHub file pulled straight from main
.
Either one needs to work out a system with tags and atomic releases, or — if one wants to have it be a live evolving project with the binaries being updated as soon as they are ready — a system that e.g. uses checksums and decides whether to update the binaries based on that.
The current setup isn't designed for an "updater", just grabbing a live file from GitHub that may or may not have anything to do with what's currently on archive.org will just result in chaos like what you are currently seeing.
Anyway, I don't want to speak for Mr. Emu, he's the one that is doing this work, but if an updater is something that should exist, this probably needs to be coordinated between you two. The binary checksum approach is the more robust and simple as far as workflow goes, but there are issues with that too.
The other complication with an updater is of course that it will overwrite your save games on the image, and also that the image will be a different checksum if it has been written to, so the binary checksum approach mentioned above will have issues with this.
There’s a reason we do versioned, atomic releases of AmigaVision — if you pulled files from any of our 1100+ commits on GitHub and just applied them to an existing image, the likelihood of that working isn’t exactly 100%.