[new release] cohttp* (2.4.0)#15241
Merged
Merged
Conversation
…http, cohttp-lwt-jsoo and cohttp-lwt-unix (2.4.0) CHANGES: - mirage: adapt to new mirage interfaces: mirage-flow 2.0.0, mirage-channel 4.0.0, mirage-kv 3.0.0 (mirage/ocaml-cohttp#678 @hannesm) - async: use Pipe.singleton instead of Pipe.of_list as it is more efficient (mirage/ocaml-cohttp#677 @smuenzel-js)
Member
Author
|
CI revdeps failure look unrelated, travis macos runner seems to have connectivity issues |
Contributor
|
Commit: 58c826c A pull request by opam-seasoned @hannesm. ☀️ All lint checks passed 58c826c
☀️ Installability check (+7)
|
Member
|
Thanks! |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
CHANGES:
mirage-channel 4.0.0, mirage-kv 3.0.0 (adapt to mirageos 3.7.0 interfaces mirage/ocaml-cohttp#678 @hannesm)
(Use Pipe.singleton in cohttp-async/body_raw mirage/ocaml-cohttp#677 @smuenzel-js)