allow happy ==2.0.2 || >=2.1.2 && <2.2 #278
Closed
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
shayne-fletcher
force-pushed
the
relax-happy-bounds3
branch
2 times, most recently
from
8f37c6a
to
3a896d1
Compare
shayne-fletcher
force-pushed
the
relax-happy-bounds3
branch
from
3a896d1
to
0f1792d
Compare
shayne-fletcher
changed the title
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.
in digital-asset#565 we allowed happy build depends < 2.1 so as to allow happy-2.0.2 (2.1 was marked deprected). since then happy 2.1.1 and 2.1.2 were released (2.1.1 is also marked deprecated). this then resulted in issue digital-asset#566 which this fixes. so, i'm changing the bounds to
happy:happy == 1.20.* || == 2.0.2 || >= 2.1.2 && < 2.2. this change puts us out of step with GHC itself which is still < 2.1 but i guess it will catch up.