Looks like v1.23.7 release is tagged v1.27.7-1,
which should be v1.23.7 instead?
Because of this (I guess,) app keeps update itself to be 1.27. but which doesn't exist.
Oops! This step is unfortunatly one which needs to be done manually in the release management process it was a typo. Sorry for the inconvience. Should be fixed by now!
Looks like v1.23.7 release is tagged v1.27.7-1, which should be
v1.23.7
instead? Because of this (I guess,) app keeps update itself to be 1.27. but which doesn't exist.