Closed sunwukonga closed 6 years ago
Thanks.
I guess we'll have to cut a release for this to show up on hackage?
Yes, I imagine that's how it works. You'll have to introduce a feature/fix a bug that is worthy of a bump :D
Thanks. I've heard tell of legends of hackage maintainers silently fixing things, and wondered whether this was one such time.
On Wed, 13 Dec 2017 at 10:26 Paul Desmond Parker notifications@github.com wrote:
Yes, I imagine that's how it works. You'll have to introduce a feature/fix a bug that is worthy of a bump :D
— You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub https://github.com/jml/graphql-api/pull/133#issuecomment-351349237, or mute the thread https://github.com/notifications/unsubscribe-auth/AAHq6qmiqRqX6NxfpdgeLnk99a6FnHVeks5s_6ZTgaJpZM4RAL3- .
You can edit package information directly on hackage: https://hackage.haskell.org/package/graphql-api/maintain
Also took the liberty to change the synopsis field. It lacked specificity.
Edited
package.yaml
then calledhpack
. Apologies for the meaningless churn ingraphql-api.cabal
.