-
-
Notifications
You must be signed in to change notification settings - Fork 15
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
Please put on Stackage #4
Comments
Hi @tsani , thanks for raising this ! github-webhooks is only a package candidate at the moment, pending further testing for the 1.0.0 release. I would like to solve #2 and #3 before releasing so that the API remains as stable as possible for the very long foreseeable future. Just before 1.0.0 is released on Hackage I will open the pull request to Stackage and it should all land quite quickly! ETA 2 weeks okay? |
@tsani we will be pushing back the roadmap a little bit on this. I'll update this soon with the new release dates. In the mean time, to correct your tsani/servant-github-webhook#9 we will release a 0.9 ASAP from a branch without resolving the 1.0.0 milestone. |
Addressed by commercialhaskell/stackage#3322 . |
Closed by commercialhaskell/stackage@b432dc6. Now available in nightly. |
Hey there! In a recent PR to servant-github-webhook, a dependency on
github-webhooks
was introduced in order to easily support a dynamically changing set of webhook keys. Currently, we have to use theextra-deps
field instack.yaml
to get it to build.Will you be adding
github-webhooks
to Stackage soon? The links to Stackage in the readme are currently 404s.The text was updated successfully, but these errors were encountered: