[new release] ppxlib (0.18.0)

[NathanReb]

Standard library for ppx rewriters

• Project page: https://github.com/ocaml-ppx/ppxlib
• Documentation: https://ocaml-ppx.github.io/ppxlib/

CHANGES:

• Bump ppxlib's AST to 4.11 (Upgrade internal AST to 4.11 ocaml-ppx/ppxlib#180, @NathanReb)

[camelus]

Commit: a099ba1

A pull request by opam-seasoned @NathanReb.

☀️ All lint checks passed a099ba1

• These packages passed lint tests: clim-ppx.0.3.0, hardcaml.v0.14.0, metapp.0.3.0, metaquot.0.3.0, mlt_parser.v0.14.0, ppx_bitstring.4.0.0, ppx_const.2.0, ppx_custom_printf.v0.13.0, ppx_custom_printf.v0.14.0, ppx_deriving_rpc.7.2.0, ppx_deriving_rpc.8.0.0, ppx_expect.v0.14.0, ppx_fields_conv.v0.14.1, ppx_getenv.2.0, ppx_irmin.2.2.0, ppx_optcomp.v0.13.0, ppx_optcomp.v0.14.0, ppx_protocol_conv.5.1.3, ppx_python.v0.13.0, ppx_sexp_conv.v0.14.1, ppx_sexp_message.v0.13.0, ppx_sexp_message.v0.14.0, ppx_yojson.1.0.0, ppxlib.0.18.0

---

☀️ Installability check (+1)

• new installable packages (1): ppxlib.0.18.0

[mseri]

@NathanReb a few revdeps seem to fail with Pconst_string having an incorrect number of arguments or similar issues, like metapp, metaquot and ppx_bitstring, can you double check if they also need an upper bound before I merge the PR?

[NathanReb]

Yeah it's expected that some other packages might break, I just added the bounds to the ones I sent patches to. I'll take a look tomorrow first thing in the morning !

[NathanReb]

Where can I look at the revdeps failures? Some of the datakit builds seem to never have actually started, including ppxlib's revdeps one :/

[mseri]

Oh no. That is really unfortunate. I think the ci was restarted overnight and we lost the previous run

[mseri]

The failures are there now. I post directly the links:

1. https://ci.ocaml.org/log/saved/docker-run-e5c6d4540c2d9cc05422d324dd854f1a/6986ad2688abc57a3ae870a14c2429704fcdf36b
2. https://ci.ocaml.org/log/saved/docker-run-88776b84cadeaf9d97377a259dcd048a/1246e3f693bc9f898bd731a51bea4c71db0aa955
3. https://ci.ocaml.org/log/saved/docker-run-a2b1acab4f2403f1b2d43b4c4038cf03/163ca9525243021b9e4deef9c5452df1bec36e33
4. https://ci.ocaml.org/log/saved/docker-run-f17b94dfcd5de6d56235ef64413297f7/b8233878856d5ed8556da2753bfe7ffbfd8d4026
5. https://ci.ocaml.org/log/saved/docker-run-1d36f70ca7b681cf3853f2afcbcee52d/0b3ed34dbc3625aa67eedef3007017437c070c99
6. https://ci.ocaml.org/log/saved/docker-run-aea7dc8b21e0b51cf1abf6adba4aea52/ab152e0c15d8951aace234adb2cea349f86177ae
7. https://ci.ocaml.org/log/saved/docker-run-105125ed0e51f66f3682d789d53372eb/90a10ac3a211e02fe33a8c1e151185199688e220
8. https://ci.ocaml.org/log/saved/docker-run-d0991f71cad891cc77ff1cb377194f88/da0cf34f4bbc1bb153220a8170beefbe5e2bdfb6
9. https://ci.ocaml.org/log/saved/docker-run-39ad3c08cfe0086005eeeb50355d714c/aff6a5774473861331ef4ddc423dea9cab8224d6

There are others, but I had checked them yesterday and they had nothing to do with this PR.

@NathanReb The links should be available until tonight, if you can please download them (the name of each package is at the top of the log)

[NathanReb]

I'll take care of it ASAP!

[NathanReb]

I think I fixed them all!

[kit-ty-kate]

Thanks a lot!