Fix cabal check for Hackage release #4528
Merged
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
|
This PR is a prerequisite for the release. |
fendor
force-pushed
the
enhance/cabal-check
branch
from
4b75a7e to
221d2bd
Compare
fendor
force-pushed
the
enhance/cabal-check
branch
from
221d2bd to
61eb7a9
Compare
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.
The current
haskell-language-server.cabalfails when runningcabal checkforcabal-install 3.12.1.0.I don't know which
cabalversion is used on Hackage, but I know that thiscabal checkwas an issue for the last Hackage release.We need to add a check to the release CI, but it is quite annoying since
cabal checkdoesn't acceptallas a target.