-
Notifications
You must be signed in to change notification settings - Fork 712
bump known ghc versions in cabal library #8260
New issue
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
Conversation
warn verbosity $ | ||
"Unknown/unsupported 'ghc' version detected " | ||
++ "(Cabal " ++ prettyShow cabalVersion ++ " supports 'ghc' version < 9.4): " | ||
++ "(Cabal " ++ prettyShow cabalVersion ++ " supports 'ghc' version < 9.6): " |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can this constant (now 9.6
) be factored out so that there is a single place where it has to be changed?
@Mergifyio rebase |
✅ Branch has been successfully rebased |
a3c3240
to
19ef31d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
bump first, bikeshed later
@Mergifyio backport 3.8 |
🟠 Waiting for conditions to match
|
2 similar comments
🟠 Waiting for conditions to match
|
🟠 Waiting for conditions to match
|
Co-authored-by: Gershom Bazerman <gershom@arista.com> Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> (cherry picked from commit af25861)
✅ Backports have been created
|
bump known ghc versions in cabal library (backport #8260)
I think that would make sense, yes. There's not the same sort of failure mode here, so I didn't catch it. (And actually, I wonder if an upper bounds check makes sense there at all tbh, given the structure of the code and how it is used) |
I don't understand the motivation, either, but I hoped somebody does. :) If nobody objects, I will kill the upper bounds check instead of updating it, when preparing 3.8.1.0 in a couple of days. In the result, GHC arguments will be normalized in any unknown too new GHC versions in the same way as in the last known GHC version, instead of not being normalized at all. |
Nobody objected, so this is what I did in #8310. |
Resolves #8230