Currently installing curl-runnings via hackage results in a compilation error because Aeson 2.0 changed their API for keys/maps.
Solution:
Put an upper bounds on Aeson and bump the incremental version number of curl runnings. Publish to hackage and now everybody can install again.
2nd Step: add a compatibility module that can morph on the fly to Aeson 1.x and 2.x. Bump the version and publish to hackage. Now everybody can install again no matter what version of Aeson they have locally.
Problem:
Currently installing curl-runnings via hackage results in a compilation error because Aeson 2.0 changed their API for keys/maps.
Solution:
Put an upper bounds on Aeson and bump the incremental version number of curl runnings. Publish to hackage and now everybody can install again.
2nd Step: add a compatibility module that can morph on the fly to Aeson 1.x and 2.x. Bump the version and publish to hackage. Now everybody can install again no matter what version of Aeson they have locally.