-
-
Notifications
You must be signed in to change notification settings - Fork 413
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
non-core servant packages for for GHC 8.10 #1331
Comments
same for servant-swagger |
cc @fisx I thought we got those to work already? |
(I edited your above comment to tag the current maintainers) |
Refs #1325 |
🙏 |
This just needs an upload. That's it: http://hackage.haskell.org/package/servant-conduit @fisx could you pair with me on this tomorrow? I never did a hackage upload before :) |
You can do just revision per 43cf589#diff-bf9e18c25e3290f6ff8a07f1af19404d via https://hackage.haskell.org/package/servant-conduit/maintain |
Same for servant-docs. This is now blocking servant-auth releases. |
I tried to do it but my hackage account doesn't seem to have enough rights. This is blocked on me getting a hold of @fisx (which shouldn't be too hard as we share an office). I'm working on it :) |
i've added you. i wonder if there is an easy way to find all servant projects' maintainers lists? |
ah, i can diff http://hackage.haskell.org/user/MatthiasFischmann and http://hackage.haskell.org/user/arianvp. i'll do that, then! |
@arianvp any luck? :) |
(forgot swagger, i'll do that next.) |
I use https://github.com/domenkozar/releaser to automate releases |
|
Many of the above packages don't have their CI updated yet to run against GHC 8.10. as they live in a separate repo. We should fix that first. Just a matter of adjusting parameters; and running |
this is too much manual work... |
I've updated the checklist above. All the packages that aren't checked off are currently broken on The ones that have been ticked off have working CI but still need a release to have a valid build plan |
@fisx @arianvp @dmjio
The text was updated successfully, but these errors were encountered: