Build against ghc-8.6
#669
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 switches to `ghc-8.6` as the new default used for both CI and local development
Collaborator
|
I dunno about this, considering the scary bug 8.6.1 has. 8.6.2 ought to be along very shortly indeed with some really important fixes, though. |
Collaborator
Author
|
@quasicomputational: How about adding a GHC 8.6.1 build just to verify compatibility but use GHC 8.4.3 for creating the tarballs and for the development environment? |
Collaborator
|
Yeah, that makes sense. Being a row in a build matrix ought to be fine, but I think we ought to be suspicious of binaries produced by 8.6.1 or relying on it for the development process. |
... as suggested by @quasicomputational
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.
This switches to
ghc-8.6as the new default used for both CI and localdevelopment