In my release cycle I provide several release candidates.
So for version 1.0, there will be several 1.0-rc#
I noticed the sorting does not take this into consideration, so it breaks above 10 release candidates as 1.0-rc9 is wrongly sorted higher than 1.0-rc10