Possibly wrong bounds for `lsp-test`

[michaelpj]

This pops up when using cabal new-build, see lukel97/lsp-test@91086de#commitcomment-33279281.

[lukel97]

Has been fixed with a revision on hackage

[michaelpj]

I'm still observing this, as is @power-fungus, even after updating my hackage index. Possibly best to just push a restriction to the bounds in this repo for now.

[samuelpilz]

There was some issue that has been solved by a hackage revision. However the issue about incorrect bounds is still present (see #1210, sorry for the duplicate issue) a quick PR #1211 fixes this issue temporarily.

[alanz]

Sometimes you have to tell stack to use a specific revision, for some reason. e.g. see monad-dijkstra in the current deps.

[fendor]

The problem is with cabal new-build, not stack, stack seems to work just fine.

[samuelpilz]

For stack we actually fix the version to the correct one.