Skip to content
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

Reenable servant-swagger, servant-openapi3 #6500

Merged

Conversation

maksbotan
Copy link
Contributor

Checklist:

  • Meaningful commit message, eg add my-cool-package (please don't mention build-constraints.yml)

  • At least 30 minutes have passed since uploading to Hackage

  • On your own machine, you have successfully run the following command (find verify-package in the root of this repo):

    ./verify-package $package # or $package-$version
    

The script runs virtually the following commands in a clean directory:

  stack unpack $package-$version # `-$version` is optional
  cd $package-$version
  rm -f stack.yaml && stack init --resolver nightly --ignore-subdirs
  stack build --resolver nightly --haddock --test --bench --no-run-benchmarks

I've updated Hackage revisions and uploaded newer servant-swagger.

CI

Our CI tries to line up build-constraints.yaml with the current state
of Hackage. This means that failures that are unrelated to your PR may
cause the check to fail. If you think a failure is unrelated you can
simply ignore it and the Curators will let you know if there is
anything you need to do.

@jkachmar jkachmar merged commit 06e6d79 into commercialhaskell:master Mar 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants