fix happy to 1.20.1.1 #559
Merged
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
fix-happy
branch
from
9702c49
to
c6a9428
Compare
shayne-fletcher
force-pushed
the
fix-happy
branch
from
c6a9428
to
229094d
Compare
samuel-williams-da
approved these changes
Sep 23, 2024
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.
happy 2.0.1 was released yesterday https://hackage.haskell.org/package/happy-2.0.1.
as indicated by these build failures https://github.com/digital-asset/ghc-lib/actions/runs/10950791602, ghc bootstrapping apparently demands happy <=happy-1.20.1.1
this PR adds the constraint
happy < 2.0toghc-lib-gen.cabalwhich enables us to recover working CI pipelines.the same constraint is also added to (generated) ghc-lib/ghc-lib-parser cabal files which fixes #557.