Allow http-types-0.12

[MichaelXavier]

I tested this locally, but I'm not really sure its the right thing to
put http-types in the default stack.yaml

This is for commercialhaskell/stackage#3232 which blocks
us in katip-elasticsearch downstream

Update: @bitemyapp I noticed you actually put the http-types-0.11 in the stack.yaml in the last commit. Should I instead put 0.12 in the stack.yaml? Wasn't sure about the policy but I may have guessed wrong.

[bitemyapp]

I noticed you actually put the http-types-0.11 in the stack.yaml in the last commit. Should I instead put 0.12 in the stack.yaml? Wasn't sure about the policy but I may have guessed wrong.

Yeah, to test that we're correctly tracking Stackage and that the build works I put http-types-0.11 in the stack.yaml. Part of the intent is to pin the latest version we're intending to work with in whatever the primary stack.yaml is at the moment. This build permits http-types-0.12 it isn't validating that the build works with that specific version. I'm quite open to alternatives.

[MichaelXavier]

That sounds like a good tradeoff to me. I'll add an explicit http-types version and see what the build says.

[MichaelXavier]

@bitemyapp Tests are green. Mind if I cut, I guess, a D-level release?

[bitemyapp]

@MichaelXavier much as I'm loathe to break things up, I think we're eating non-linear Generics pain in the Types modules. Might it be worth to split them into constituent modules to ease compile times? I hate bouncing the CI on this library.

[bitemyapp]

Mind if I cut, I guess, a D-level release?

Yeah go ahead, thanks for covering this!

[MichaelXavier]

I've created #222 to discuss the compile time issue.

[MichaelXavier]

Released at 0.15.0.2