Repository navigation
semver range seems to not calculate correctly for comparison operators #2340
Description
^7.5 <7.6 matches 7.6, this seems unintentional.
(Same for ~7.5 matching 7.6)
(Example taken from the prisma package page)
^7.5 <7.6 matches 7.6, this seems unintentional.
(Same for ~7.5 matching 7.6)
(Example taken from the prisma package page)
Activity
joshuaisaact commentedon Apr 5, 2026
Hey so I fixed this in the above PR. It turns out we were always adding the latest version at the end of the filter array.
It might be that was intentional, but I think I agree with you - it doesn't really make much sense, from a UX perspective.
If I filter by semver I should only see the semvers I want to filter by, I shouldn't always see latest too.
denis-sokolov commentedon Apr 5, 2026
Thank you!
Yes, I was fully confused by the feature and I thought I can not trust the results given what it was showing.
If we want to always show the latest, I would visualize it. E.g. move the latest version above the search field.