[new release] conduit-lwt-tls, conduit-mirage, conduit-tls, conduit-lwt, conduit-async-tls, conduit-async, conduit, conduit-async-ssl and conduit-lwt-ssl (3.0.0)

[dinosaure]

A portable network connection establishment library using Lwt and ocaml-tls

• Project page: https://github.com/mirage/ocaml-conduit

CHANGES:

• breaking change - New version of conduit. Most of the new API has a
  description on the pull-request
  mirage/ocaml-conduit#311. Documentation is
  updated as well with a small HOW-TO (available
  here) which
  describes the new API.

[dinosaure]

Redo #17417.

[camelus]

Commit: 84bbef9

A pull request by opam-seasoned @dinosaure.

☀️ All lint checks passed 84bbef9

• These packages passed lint tests: conduit-async-ssl.3.0.0, conduit-async-tls.3.0.0, conduit-async.3.0.0, conduit-lwt-ssl.3.0.0, conduit-lwt-tls.3.0.0, conduit-lwt.3.0.0, conduit-mirage.3.0.0, conduit-tls.3.0.0, conduit.3.0.0

---

☀️ Installability check (+9)

• new installable packages (9): conduit.3.0.0 conduit-async.3.0.0 conduit-async-ssl.3.0.0 conduit-async-tls.3.0.0 conduit-lwt.3.0.0 conduit-lwt-ssl.3.0.0 conduit-lwt-tls.3.0.0 conduit-mirage.3.0.0 conduit-tls.3.0.0

[mseri]

Now that there are no-longer revdeps, due to the upper bounds everywhere, the only thing that needs to be checked is that conduit-* builds also on ocaml 4.07 (which is not tested in the conduit CI). If that is the case (I have not tried, and cannot at the moment) should we merge and release the ocaml CI?

[dinosaure]

Now that there are no-longer revdeps, due to the upper bounds everywhere, the only thing that needs to be checked is that conduit-* builds also on ocaml 4.07 (which is not tested in the conduit CI). If that is the case (I have not tried, and cannot at the moment) should we merge and release the ocaml CI?

I'm not sure, as far as I can tell, all should works - build & tests work. So I will happy to definitely merge it (and unlock several PR). May be @kit-ty-kate has some clue about the state of the CI?

[mseri]

It’s all green!