Skip to content

Conversation

@mergify
Copy link
Contributor

@mergify mergify bot commented Jul 14, 2024

When updating to GHC 9.10 (#9914), we had to put a bunch of allow-newer's and pull some patches from head.hackage. This shouldn't be needed after the ecosystem has caught up. This PR shows that the only issue remaining is rere (ulysses4ever/rere#28).

We didn't apply the bandaids (allow-newer's and head.hackage source repo) unconditionally and instead used impl(ghc >= 9.10.0). Now, we don't remove this stuff, we bump the conditional from 9.10.0 to 9.12.0 anticipating the same procedure for the future (yet unplanned) release of GHC 9.12.

Template B: This PR does not modify behaviour or interface

E.g. the PR only touches documentation or tests, does refactorings, etc.

Include the following checklist in your PR:

  • Patches conform to the coding conventions.
  • Is this a PR that fixes CI? If so, it will need to be backported to older cabal release branches (ask maintainers for directions).

This is an automatic backport of pull request #10194 done by [Mergify](https://mergify.com).

* CI: don't allow-newer for GHC 9.10

* allow-newer base for rere

* buildinfo-reference-generator: bump base bound

* cabal-testsuite: bump base bound

(cherry picked from commit cb34d2a)
@mergify mergify bot mentioned this pull request Jul 14, 2024
2 tasks
@mergify mergify bot added the backport label Jul 14, 2024
@geekosaur geekosaur added the merge me Tell Mergify Bot to merge label Jul 17, 2024
@mergify mergify bot merged commit ece1234 into 3.12 Jul 17, 2024
@mergify mergify bot deleted the mergify/bp/3.12/pr-10194 branch July 17, 2024 23:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport merge me Tell Mergify Bot to merge

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants