-
-
Notifications
You must be signed in to change notification settings - Fork 322
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.
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
support GHC 8.6 / get into stackage nightly #883
Comments
Is there still anything blocking this issue from making progress? |
It looks like at least hledger can get into stackage. Working on it now. |
Ah.. yes, of course the released hledger 1.11 doesn't support GHC 8.6. The required code and dep changes are involved enough that (a) I'd prefer not to spend that time if I don't have to and (b) they may require more than a minor version bump. On the other hand, it's still quite a long time until next scheduled release (12/31). Hmm. |
Will there be a new version of hledger that support ghc 8.6.x? It's been quite a while since 8.6.x came out, but the current release hledger still doesn't support it even though the incompatibilities seem rather small'ish in nature. |
Yes, and thanks for the ping. I have been grinding on release prep and aim to release 1.12 on or close to 12/1.
… On Nov 29, 2018, at 6:32 AM, Peter Simons ***@***.***> wrote:
Will there be a new version of hledger that support ghc 8.6.x? It's been quite a while since 8.6.x came out, but the current release hledger still doesn't support it even though the incompatibilities seem rather small'ish in nature.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
OK, very cool! Thank you for your efforts. |
hledger 1.12.1 released, |
Stackage-related followup issues noted above, but we are back in stackage at last \o/ so closing this. |
hledger 1.10 was in stackage nightly-2018-09-28, since then we and a thousand others have been removed pending GHC 8.6 buildability.
The text was updated successfully, but these errors were encountered: