More permissive lower bound for resourcet #40
Merged
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
This was referenced Aug 27, 2023
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.
1.3.0 lowerbound for resourcet unnecessarily excludes versions with which the package is working fine.
We're using stack lts-20.26 (based on ghc-9.2.8) which has resourcet-1.2.6.
When I add resourcet-1.3.0 to extra-deps in stack.yaml to use newer version from hackage, I get bunch of other version conflicts (e.g. servant-server-0.19.2 from stack lts permits resourcet >=1.2.2 && <1.3 :/
Long story short, let's please lower resourcet bound before releasing.