The release plugin should correctly mark the latest release #77
Description
In the latest Spring Security release, 6.4.8 was marked as the latest release, even though 6.5.2 was also released.
I wonder if 6.5.2 finished first, marked itself as the latest, and then 6.4.8 did the same thing.
I think each release in a generation should check if there are releases of a higher number before marking themselves as the latest.