-
Notifications
You must be signed in to change notification settings - Fork 113
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
hnix 0.12.0.1 fails to build with hashable 1.3.1.0 #855
Comments
Thank you Simon. Indeed, recently removed a couple of them. In current situation would kick the Since https://github.com/haskell-nix/hnix/blob/fccb88604179c76d43610be07af58226ac8f0615/ChangeLog.md is a huge change, see, do not want to dump it on people. The fix branch and release going to be made. |
The last two major package versions got new revisions. Also seems a good idea to have the CI regularly check the Hackage package. |
Oh, well. I cant release from the fix branch, removing the instance technically is an API breakage. ... But if it just gets reexported from But that reexport in the minor version may break the downstream somewhere, if they would import the |
Do not bother everyone with minor things, I do not want to do major release for 1 And then thought: why chose any of the two. Up to 3 days ago somehow everyone was casually living without that instance. In some near time, the major release would be ready. Migration helper automation needs to be done before the release. And maybe it worth waiting guys in #804 would show up to packs everything into one major. |
Can we close this? Is revision enough for you for ~2 month? |
Sorry, was thinking about other things. |
Thanks for the quick reaction @Anton-Latukha! Could you possibly add a revision for v0.12.0 too? http://hackage.haskell.org/package/hnix-0.12.0 Note that |
Of course, the 9.0 work also is great to include in major. Happy to see you, in GHC, in main libs, and everywhere. Done |
Thank you also for upstreaming the |
Probably is closed now. |
This instance was added to
hashable
in v1.3.1.0. I see that the orphan instance has already been removed onhnix
master
(yay!), so a new release should fix this.The text was updated successfully, but these errors were encountered: