aeson intentionally held back to 0.9.*

[DanBurton]

Issues with aeson-0.10.0.0 have put us in an awkward place. Starting immediately, nightly builds will be stepping back to aeson-0.9. Unfortunately, some downstream packages are going to suffer the consequences. In the past we asked you to support building against aeson-0.10.0.0. We are backtracking that request. Your packages don't have to build against aeson-0.10.0.0. Instead, we are asking you to support building against aeson-0.9 again.

The following are excluded from nightly builds:

• bloodhound @bitemyapp
  • Please release a version of bloodhound that simultaneously supports aeson-0.9.0.1, http-types-0.9, and semigroups-0.18.0.1 in order to be restored to stackage.
• hoauth2 @freizl
  • Please release a version of hoauth2 that simultaneously supports aeson-0.9.0.1 and http-types-0.9 in order to be restored to stackage.
• yesod-auth-oauth2 @benekastah
  • Please wait for or contribute to the requested changes to hoauth2 in order to be restored to stackage. Sorry.

The following are held back to old versions on nightly builds:

• postgresql-binary < 0.7 @nikita-volkov
• hasql < 0.8 @nikita-volkov

If a new version of postgresql-binary is released that supports aeson-0.9.0.1, then these two restrictions can be lifted.

Due to issues with aeson-0.10.0.0, we are planning on discontinuing LTS 4. Next Sunday (2016-01-24) we will begin LTS 5 which will ship with aeson-0.9.

@bitemyapp and @freizl, if you cannot meet the 1 week deadline, your package won't be included in lts-5.0, but can potentially be added to lts-5.1 or later.

@nikita-volkov, we have a few options to choose from with those two packages of yours:

1. stick to those old versions as listed above for lts 5
2. release a new version of postgresql-binary within a week that works with aeson-0.9
3. exclude those two packages from the initial release of lts-5, but include them in lts-5.1 or later

The nightlies are going to run with option 1 for a few days, but if I don't hear from you promptly, I'll go with option 3 by default.

[freizl]

sounds disappointed but will make it for hoauth2.

[nikita-volkov]

I've update the "postgresql-binary" package

[freizl]

hoauth2-0.5.2 shall be good.

[DanBurton]

Thanks for the quick responses! Assuming the nightly build goes well, the only downstream package left to worry about is bloodhound.

[DanBurton]

@nikita-volkov There was a build issue with the new postgresql-binary, so I temporarily disabled it and hasql. See nikita-volkov/postgresql-binary#4

[nikita-volkov]

@DanBurton It's fixed now.

[DanBurton]

@nikita-volkov 👍 I've enabled them again.

[DanBurton]

bloodhound is the only straggler; I've opened up an issue on its tracker with the pertinent instructions. I'm going to close this issue now, but we'll continue with the constraint aeson < 0.10 until a new version is released that the whole community can adequately support.