We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
head.hackage
Currently, generating a CI job for GHC 9.10 will cause it to use head.hackage by default:
if [ $((HCNUMVER >= 91000)) -ne 0 ] ; then echo "HEADHACKAGE=true" >> "$GITHUB_ENV" ; else echo "HEADHACKAGE=false" >> "$GITHUB_ENV" ; fi
This is a consequence of this code:
haskell-ci/src/HaskellCI/HeadHackage.hs
Lines 7 to 8 in 07deeb7
Now that GHC 9.10.1 is fully released, should this be changed so that 9.10.1 doesn't require head.hackage, just like other full GHC releases?
The text was updated successfully, but these errors were encountered:
Ouch. Thanks for spotting this! I'll make a fix asap.
Sorry, something went wrong.
Now that GHC 9.12.1 has been released, I think we need to do something similar by defining defaultHeadHackage = C.orLaterVersion (C.mkVersion [9,13]).
defaultHeadHackage = C.orLaterVersion (C.mkVersion [9,13])
head.hackage>=9.13
cd844d5
See haskell-CI#725 (comment)
Successfully merging a pull request may close this issue.
Currently, generating a CI job for GHC 9.10 will cause it to use
head.hackage
by default:This is a consequence of this code:
haskell-ci/src/HaskellCI/HeadHackage.hs
Lines 7 to 8 in 07deeb7
Now that GHC 9.10.1 is fully released, should this be changed so that 9.10.1 doesn't require
head.hackage
, just like other full GHC releases?The text was updated successfully, but these errors were encountered: