v1.0.9-r4: use major-major upper bounds only #82
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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 |
Per the README & haskell/cabal#5170 it is only necessary for Cabal < 2.4 ( 2018 ).
The examples / tests can stay on major-major bounds: this'll help detect issues earlier, on CI.
|
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/ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.