Aeson problem (#74)

* Put an uppor bounds on Aeson for now

Problem: Aeson 2.0+ came out with a vuln fix. Unfortunately it is a breaking
change. This causes curl-runnings to fail to compile if you just grab a fresh
GHC installation and try to `cabal install curl-runnings`

Solution (in two steps):
1. Put an upper bounds on aeson and push a point release (0.16.4).
2. Fix the aeson compilation with CPP directives pivoting on the version of
Aeson and release a new minor version (0.17.x)

(cherry picked from commit 62fae2071c562e7cf745f3b9142225c90e432cf7)

* Bumping the incremental version of curl-runnings

(cherry picked from commit 520010af396ee0b8e2e08fb976b774f3397f1e6d)

Author: dysinger

package.yaml

@@ -1,5 +1,5 @@
 name:                curl-runnings
-version:             0.16.3
+version:             0.16.4
 github:              aviaviavi/curl-runnings
 license:             MIT
 author:              Avi Press
@@ -28,7 +28,7 @@ library:
   - Testing.CurlRunnings.Internal.KeyValuePairs
   - Testing.CurlRunnings.Internal.Payload
   dependencies:
-  - aeson >=1.2.4.0
+  - aeson >=1.2.4.0 && <2.0
   - bytestring >=0.10.8.2
   - case-insensitive >=0.2.1
   - base64-bytestring >=1.0.0.2
@@ -65,7 +65,7 @@ executables:
     - base >=4.7
     - cmdargs >=0.10.20
     - directory >=1.3.0.2
-    - aeson >=1.2.4.0
+    - aeson >=1.2.4.0 && <2.0
     - http-conduit >=2.2.4
     - bytestring >=0.10.8.2
     - curl-runnings
@@ -85,7 +85,7 @@ tests:
     - bytestring >=0.10.8.2
     - curl-runnings
     - directory >=1.3.0.2
-    - aeson >=1.2.4.0
+    - aeson >=1.2.4.0 && <2.0
     - hspec >= 2.4.4
     - hspec-expectations >=0.8.2
     - raw-strings-qq >= 1.1