Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

aeson 1.2 compatibility #180

Closed
bitemyapp opened this issue Apr 18, 2017 · 3 comments
Closed

aeson 1.2 compatibility #180

bitemyapp opened this issue Apr 18, 2017 · 3 comments
Assignees
@bitemyapp

Comments

@bitemyapp
Copy link
Owner

per commercialhaskell/stackage#2449
@bitemyapp bitemyapp self-assigned this Apr 18, 2017
@bitemyapp bitemyapp mentioned this issue Apr 19, 2017
Merged
@23Skidoo
Copy link
Contributor

cabal new-build --enable-test --allow-newer=aeson completes successfully with 0.12.1.0, so it'd be nice if you could bump the Hackage upper bound on aeson for that version as well.

@bitemyapp
Copy link
Owner Author

@23Skidoo No, mutating previously released packages is bad. You don't have my consent to edit it either.

@bitemyapp
Copy link
Owner Author

This is fixed with the release of 0.14.0.0.

Repository owner locked and limited conversation to collaborators Apr 24, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@bitemyapp bitemyapp

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@23Skidoo @bitemyapp