Open and-pete opened 3 years ago
Hi, thanks for letting me know!
I probably won't have time to get to this in the next couple weeks, but if you (or anyone else reading this) is interested in figuring this out, please go ahead!
My guess is that for some reason servant-rawm
is held back to an earlier version in stackage (possibly because of bounds on servant
or something?). Or possibly just because I never actually added the servant-rawm-{server,client,docs}
packages into stackage?
Please feel free to send PRs to stackage adding servant-rawm-{server,client,docs}
, or removing the unneeded version bounds, and cc me as well.
Hello! :)
I notice that the combined
servant-rawm-1.0.0.0
package (here) is currently still the version in the Stackage snapshot (currently for both the recent LTS-17.x series and the nightly builds). Looking for any of the now-divided packages however (e.g. servant-rawm-server) says that they've never been in a snapshot and that the latest version on Hackage is1.0.0.1
.Will
servant-rawm-{server,client,docs}-1.0.0.1
be making it into a future Stackage snapshot?I'm currently pointing toward a commit hash in my
stack.yaml
and that's working just fine for me, but I was thinking that perhaps you weren't aware that they weren't being included.Thanks! :)