Closed SinisterRectus closed 7 years ago
I believe this is a result of the SemVer matching algorithm used. Doesn't seem ideal for this scenario.
Relevant code from deps/semver.lua:
-- Given a semver string in the format a.b.c, and a list of versions in the
-- same format, return the newest version that is compatable.
-- ...
-- For x.y.z-b, match minor, patch, and build updates
assert(match("1.0.0", iterator()) == "1.1.3")
Yes, the matching is working as designed. I'm really sorry this broke. Seems the best path forward is to fix coro-http and publish a new patch version asap.
Closing this in favor of #200.
Attempting to install version 2.1.1 of coro-http installs 2.2.0 instead:
For comparison, I can install version 2.2.1 of coro-channel instead of 3.0.0: