Following from https://github.com/bos/aeson/issues/503.
aeson-1.1.0.0 (Adam Bergmark adam@bergmark.nl @bergmark) is out of bounds for:
Updated: February 1rst, 2017
smoothie fixed.
microlens-aeson fixed.
req, slug, and stache should be OK now.
pusher-http-haskell fixed.
I suspect that avers is compatible and only requires a dependency bounds bump. But I can't be sure, I can't actually buildavers because it depends on servant and a version that is compatible with aeson-1.1 has not been released yet.
Will there be enough time between servant releasing a version I can test against and stackage bumping the bounds of aeson, or should I simply bump the upper bounds and hope everything continues to work?
@wereHamster did you try building avers+servant with allow-newer in cabal-install/stack? If that works you can safely bump it. But in general we should try to improve the process so we don't disable packages that haven't gotten a notification.
@bergmark yes, that worked. Though I was confused at first because stack didn't recognize that option on the commandline, neither stack --allow-newer build nor stack build --allow-newer worked. I had to put the option into stack.yaml.
The upper bound is already adjusted on hackage.
twitter-feed fixed.
cayley-client, glabrous fixed.
hpc-coveralls fixed.
ua-parser fixed. Working on bloodhound which should fix katip and katip-elasticsearch.
bloodhound-0.12.1.0 works now, and thus katip-0.3.1.4 and katip-elasticsearch-0.3.0.2.
rethinkdb-2.2.0.8 works
Waiting on PR to be merged for hailgun:
https://bitbucket.org/robertmassaioli/hailgun/pull-requests/19/bump-aeson-version/diff
Fixed in clash-lib-0.7
Fixed in eventstore-0.14.0.1
Fixed clckwrks, clckwrks-plugin-page, userid, and happstack-authenicate.
Fixed in cayley-client-0.4.0
Fixed for haskell-tools-*-0.5
Fixed for hoauth2-0.5.8
Fixed for aeson-injector-1.0.7.0
servant-swagger and servant-swagger-ui updated
LTS 8 will be released soon, probably with aeson-1.0.2.1.
After the LTS 8.0 release, the packages listed below (and any that depend on them) will continue to be included in LTS 8 builds, but will be dropped from nightly builds until a release compatible with aeson-1.1.0.0 is made available.
aeson-1.1.0.0 (Adam Bergmark adam@bergmark.nl @bergmark) is out of bounds for:
hailgun currently has support for aeson-1.1, it just needs a release to Hackage. I gave the maintainer a little nudge here:
https://bitbucket.org/robertmassaioli/hailgun/pull-requests/19/bump-aeson-version/diff#comment-31241115
opaleye fixed.