Closed juhp closed 4 years ago
I don't find this failure when I compile from the source. Are you building with genvalidity-property >=0.5
?
My bounds are not perfect, it seems, but let's figure out what they should be before I go around making more releases frantically.
If you're going to use a new version of genvalidity-hspec
, then you might as well use the newest version of genvalidity-property
, no?
Why are you not using >=0.5
?
Because we started Stackage LTS 14 with genvalidity-property 0.4 and we generally don't allow major version bumps in LTS. Anyway I added a constraint on genvalidity-hspec for now.
Aha! How should I go about preventing stuff like this from happening? Is there anything I should do now?
You could revise your .cabal file on Hackage to stricten the lowerbound.
genvalidity-hspec-0.7.0.3
has fixed this.
While building for Stackage LTS 14:
Same for 0.7.0.1