Closed tom-audm closed 3 years ago
Hey,
I am on holiday at the moment, so I have limited Internet access. I can't remember on top of my head if the aeson bound was introduced as a precaution or because this library genuinely needs to be patched to support newer aeson.
In the former case, I can simply publish a Hackage revision to bump the upper bound. Have you tried building the library with newer version using allow-newer
or similar? Did it work?
Fixed in https://github.com/adinapoli/mandrill/commit/3e57e9a2851df70a21ffe96c0cca14a575923334, we've been using this library at CircuitHub with allow-newer: mandrill:aeson
for ages. I'll cut a new release now.
Fixed in mandrill-0.5.5.0
Aeson 1.5 is almost a year and a half old - can we bump this dependency?