Skip to content

Conversation

Mistuke
Copy link
Contributor

@Mistuke Mistuke commented Jan 14, 2024

No description provided.

@tbidne
Copy link

tbidne commented Apr 10, 2025

Hi, just wondering if there is anything I can do to help push this along? Ideally, I think what would happen here is:

  • This PR is merged and released as a new minor version e.g. 2.14.2.0.
  • 2.14.0.0 and 2.14.1.0 are revised on hackage to base >= 4.12.0 (GHC >= 8.6.1), so that the solver does not pick them.

Does that make sense?

@Mistuke
Copy link
Contributor Author

Mistuke commented Jun 24, 2025

@tbidne that does make sense. I don't remember why I didn't merge this before (and missed your reply sorry!)

I'll merge and see if there's any more work left

@Mistuke Mistuke merged commit b6499c2 into master Jun 24, 2025
@tbidne
Copy link

tbidne commented Jun 24, 2025

No problem, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants