Started by GitHub push by Geolykt6ee51f8d6cd8430c2ba78dd4657929f655993a1dfee51f8d6cd8430c2ba78dd4657929f655993a1dfrefs/remotes/origin/mainee51f8d6cd8430c2ba78dd4657929f655993a1dfee51f8d6cd8430c2ba78dd4657929f655993a1dfrefs/remotes/origin/mainee51f8d6cd8430c2ba78dd4657929f655993a1dfee51f8d6cd8430c2ba78dd4657929f655993a1dfrefs/remotes/origin/mainhttps://github.com/stianloader/PicoResolve.githttps://stianloader.org/jenkins/view/all/job/picoresolve/6/artifacthttps://stianloader.org/jenkins/view/all/job/picoresolve/changeshttps://stianloader.org/jenkins/view/all/job/picoresolve/6/https://stianloader.org/jenkins/view/all/job/picoresolve/6/testReportfalse#61815523188picoresolve #66falsefalse6128SUCCESS1714420138830https://stianloader.org/jenkins/view/all/job/picoresolve/6/src/main/java/org/stianloader/picoresolve/internal/meta/VersionCatalogue.javaee51f8d6cd8430c2ba78dd4657929f655993a1df1714419916000https://stianloader.org/jenkins/user/geolyktGeolyktadmin@geolykt.deResolve version ranges by newest version This behaviour might be a bit counterintuitive to some, completely intuitive to others. Truth be told I haven't checked what maven thinks about this all but I'd say that this is the most intuitive way of solving the problem for me (as otherwise the version would be known, so why go with a version range?). Of course the risk I'm taking with this commit is that versions may break other versions, but in reality anyone making use of version ranges should be very aware of this serious risk. 2024-04-29 21:45:16 +0200ee51f8d6cd8430c2ba78dd4657929f655993a1dfResolve version ranges by newest versioneditsrc/main/java/org/stianloader/picoresolve/internal/meta/VersionCatalogue.javagithttps://stianloader.org/jenkins/user/geolyktGeolyktgeolykt