In #11275 I tried to fix this, but discovered that the Version model actually sorts the queryset descending for some reason.

• Add version slug filtering to APIv3 #11275

We don't know why the ordering is descending, and more confusing is that tests seem to pass as we would expect already. Changing the ordering direction on the model actually breaks tests with results like stable ordered before latest.

This is still a bug, and I notice this on the project version filter dropdown, which uses the version queryset directly:

Though note, I might fix this at the filter to resolve the bug I noticed, but the underlying model is still backwards as you might notice in API responses too.