-
Notifications
You must be signed in to change notification settings - Fork 24
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
Support GHC 9.10 #82
Support GHC 9.10 #82
Conversation
Optimistic strategy: assume that nothing breaks if dependencies bump their major version (unless they bump the major-major version). Breakage can then be addressed by Hackage revisions.
It would be nice to revise |
Hi @andreasabel! I've fixed the CI for GHC 9.10. We're ready for revision 4 here. (Per #79, repo transfer was done today; I'd appreciate if you let me upload the revision myself, to get practice) I'm happy with major-major bounds in the examples / tests — but in the main lib, I'm reverting to |
Looking forward to the new version release! |
@phadej could you possibly add @ulidtko to maintainers? https://hackage.haskell.org/package/cabal-doctest/maintainers/ |
Done! |
The examples / tests can stay on major-major bounds: this'll help detect issues earlier, on CI.
Per the README & haskell/cabal#5170 it is only necessary for Cabal < 2.4 ( 2018 ).
Thanks @andreasabel 🙏 I'm going to merge this, but will actually release another version, rather than a metadata revision. Because there was a code change in 009a688 — albeit small, strictly speaking it steps beyond applicability of hackage revisions mechanism, IIUC. |
Optimistic strategy: assume that nothing breaks if dependencies bump
their major version (unless they bump the major-major version).
Breakage can then be addressed by Hackage revisions.