Adapt to conduit 2.3

[samoht]

Adapting to mirage/ocaml-conduit#376 and mirage/ocaml-cohttp#742

[dinosaure]

I'm ok to merge but small details remains. I would like to have the opinion/CI result from @TheLortex too.

[hannesm]

I'm very much in favor to get this merged and released, especially with the situation now: mirage 3.10 emits conduit >= 2.2.0 & < 3.0.0 dependencies, which install conduit 2.3.0 (and cohttp 4.0.0), and compilation fails (try to compile e.g. https://github.com/roburio/dns-letsencrypt-secondary with an up-to-date opam-repository).

In the future, we should bump major revisions (i.e. conduit-mirage 2.3.0 should be 3.0.0 (or 4.0.0 in case the unavailable 3.0.0 is supposed to stay there) when the API changes.

[dinosaure]

I'm very much in favor to get this merged and released, especially with the situation now: mirage 3.10 emits conduit >= 2.2.0 & < 3.0.0 dependencies, which install conduit 2.3.0 (and cohttp 4.0.0), and compilation fails (try to compile e.g. https://github.com/roburio/dns-letsencrypt-secondary with an up-to-date opam-repository).

Me too 👍 I will try to update the PR from my comments.

[dinosaure]

I think it's ready to merge, it's ok to merge as is? (@hannesm, @samoht) and cut a release?

[hannesm]

I have not reviewed this patch, nor followed conduit / cohttp API changes, nor tested this patch to work (but I trust you & Thomas). Looking at the mirage.mli changes in this PR this looks fine (and very backwards-compatible). A merge and release would be great.

[dinosaure]

I tested locally and it's work, let's merge.