Package proton.1.0.11

[mfreeman451]

proton.1.0.11

High-performance OCaml driver for Timeplus Proton (ClickHouse native protocol)
A feature-rich OCaml driver for Timeplus Proton, supporting streaming queries, async inserts, compression (LZ4/ZSTD), TLS security, connection pooling, and rich data types including Arrays, Maps, Enums, and DateTime64.

---

• Homepage: https://github.com/mfreeman451/proton-ocaml-driver
• Source repo: git+https://github.com/mfreeman451/proton-ocaml-driver.git
• Bug tracker: https://github.com/mfreeman451/proton-ocaml-driver/issues

---

🐫 Pull-request generated by opam-publish v2.5.1

[jmid]

Thanks!

CI summary:

• 2 opam-2.0 failures
• a 32-bit failure during @runtest (I've made a suggestion to address this)
• a Windows failure during the install of conf-liblz4 (currently not supported on Windows)

Overall Lgtm!

Would you consider adding an x-maintenance-intent entry?
https://github.com/ocaml/opam-repository/blob/master/governance/policies/archiving.md

[mfreeman451]

Thanks for the feedback once again @jmid, any advice on how the win32/liblz4 stuff? Can I avoid that test some how?

[jmid]

Thanks for the feedback once again @jmid, any advice on how the win32/liblz4 stuff? Can I avoid that test some how?

This is now down to just

• two opam-2.0 failures and
• a Windows MinGW failure during installation of conf-liblz4

As such, it is not a problem with your package, and it should not count against merging it!
There's a lot of packages that need support for MinGW and we just haven't gotten to updating them all. I might take a stab at conf-liblz4 one of the next days.
If you wait, this PR can be rebased afterwards. Alternatively, your package should start working once conf-liblz4 is fixed (unless other issues show up). As such, I'm a bit hesitant about disabling proton on Windows up front... 🤷