Extension is upgraded to the latest available version if no shell version match is available
Some of the users of the extension I maintain got upgraded to the latest version although this one was not supporting their shell version (read more here).
But no revision was actually supporting it.
The status was this one (ignore v24 which I uploaded later to fix the problem):
So, no version was explicitly supporting 3.28 and 3.30, but people on such shell versions got upgraded to v23, while in such case I'd expect the server to just request no action at all.
Edited by Marco Trevisan