[new release] ppxlib (3 packages) (0.36.1)

[NathanReb]

Standard infrastructure for ppx rewriters

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

CHANGES:

• Fix ppxlib driver's AST to source printer. Our copy of pprintast was not
  properly updated which resulted in incorrect printing of value bindings'
  constraints (Fix pprintast for 5.2 AST ocaml-ppx/ppxlib#585, @NathanReb)

[NathanReb]

CC @hhugo you should be able to use this release for gen_js_api!

[mseri]

These failures look surprising, and were not there before:

fstar.2025.06.20 (failed: Syntax error: ')' expected)
gen_js_api.1.1.1 (failed: Syntax error: ')' expected)
gen_js_api.1.1.2 (failed: Syntax error: ')' expected)
gen_js_api.1.1.3 (failed: Syntax error: ')' expected)
gen_js_api.1.1.4 (failed: Syntax error: ')' expected)
gen_js_api.1.1.5 (failed: Syntax error: ')' expected)

[NathanReb]

Ah right, that's on me!

These are expected as we updated our pprintast copy, which unfortunately prints those differently, but I should have added upper bounds.

To be a bit more specific, gen_js_api tests already break with 0.36.0. I think this was not caught back then because it was simply not compatible with 0.36.0 at all.

I'm not sure what the right fix should be here. gen_js_api.1.1.4 is not compatible with ppxlib >= 0.36.0. gen_js_api.1.1.5 builds with ppxlib >= 0.36.0 but the tests won't work:

• with ppxlib.0.36.0: the output is entirely wrong because our pprintast was bugged
• with ppxlib.0.36.1: the output is slightly off because our pprintast was properly updated but prints ASTs slightly differently then before (just as the compiler does if I'm not mistaken).

To put it simply, gen_js_api1.1.5 test won't ever work. We'll have to wait for a new release that properly updates the tests expected output.

I'll look into the fstar failures!

[NathanReb]

Removed the ppxlib-bench package, this was inadvertently added!

[NathanReb]

Ah my bad, misread the CI failures. It seems that there are two distinct problems here: the one mentioned above and the fact that pprintast spits out code that doesn't parse in 4.14 anymore. I'll investigate and see what we can do!