Haddock upper bound #1492
Merged
Haddock upper bound #1492
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
We should do a quick build without hackage index to catch those errors earlier, users can build from hackage without a fixed hackage-index (and it is not usual set it!) |
|
@Mergifyio backport 1.0.0-hackage |
|
Command
|
|
Ha mergify.io does a 👍 to ack, what a good boy |
pepeiborra
approved these changes
Mar 4, 2021
mergify bot
pushed a commit
that referenced
this pull request
Mar 4, 2021
* Add haddock upper bound * Update index to get haddock last version (cherry picked from commit d519c3c)
|
Command
|
mergify bot
added a commit
that referenced
this pull request
Mar 4, 2021
* Add haddock upper bound * Update index to get haddock last version (cherry picked from commit d519c3c) Co-authored-by: Javier Neira <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See #1470