-
Notifications
You must be signed in to change notification settings - Fork 723
Preflight checks for 3.16.1.0 #11275
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
ulysses4ever
left a comment
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.
Terrific, thanks!
geekosaur
left a comment
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.
There have been coordinated changes between Cabal and cabal-install that require cabal-install to use the new Cabal, IIRC. (#11101, which is a critical bug fix) So the bound on Cabal needs to be bumped as well. This won't be seen in CI because the one in the project will always be used.
geekosaur
left a comment
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.
On second thought, that won't matter on master, but it needs to be done in the backport.
|
@mergify backport 3.12 |
✅ Backports have been created
|
|
Backporting manually in #11280 for |
|
@mergify backport 3.14 |
✅ Backports have been created
|
Nothing much to do:
cabal-versionas this is a minor release.cabal build --allow-newer -cQuickCheck==2.17.1.0 …works with the relevant targets.If so, it will need to be backported to older cabal release branches (ask maintainers for directions).