Overview:

In case a x.y.0 is version is released which causes CI failures when it is picked up as "earlier version" for CI runs for x.y+1.z version, we should be able to fix this with a z-bump.

But the code which is currently responsible for looking up the earlier version only cares about the x.y part, not about the z part.

The logic responsible for resolving the earlier version should be improved to also take the z-part into account.