Add upper bound to hlint #1795
Merged
Add upper bound to hlint #1795
Conversation
This file contains hidden or 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
Member
jneira
commented
May 4, 2021
jneira
commented
- Without the upper bound, cabal picks hlint-3.* which brings ghc-lib-9.* causing compile errors (what this has not been catched by ci before?)
- This has to be backported to hackage-1.1.0 to make progress towards Hackage release of 1.1.0 #1774
Member
Author
|
@Mergifyio backport 1.1.0-hackage |
Contributor
|
Command
|
Ailrun
approved these changes
May 4, 2021
mergify bot
pushed a commit
that referenced
this pull request
May 5, 2021
Co-authored-by: Junyoung/Clare Jang <jjc9310@gmail.com> (cherry picked from commit ee7b5a9)
Contributor
|
Command
|
jneira
added a commit
that referenced
this pull request
May 5, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.