Possible bug found in 1.5.01

It’s complicated, but basically it was a installer issue not a code bug and the way we build things bumping the version didn’t make sense.
Besides, anyone stuck with the issue couldn’t actually be notified that there was an update so wouldn’t know to download it.
We very much try not to just replace the installer with the same version but sometimes it’s what makes the most sense.