[new release] pp (2.0.0)

[mbarbin]

Pretty-printing library

• Project page: https://github.com/ocaml-dune/pp
• Documentation: https://ocaml-dune.github.io/pp/

CHANGES:

• Prepare release (Prepare release ocaml-dune/pp#21, @mbarbin)

  • Upgrade to ocamlformat.0.26.2.
  • Fmt the code
  • Add CI badge to README
  • Upgrade GitHub workflow actions dependencies (checkout@v4, setup-ocaml@v3)
  • Add more validation steps in CI
  • Add ocamlformat as dev-setup dependency

• Add Pp.verbatimf. (add Pp.verbatimf ocaml-dune/pp#18, @mbarbin)

• Add Pp.paragraph and Pp.paragraphf (fix: type of Pp.paragraphf and add changelog ocaml-dune/pp#19, @Alizter)

• Remove of_fmt constructor. (refactor: remove Format constructor ocaml-dune/pp#17, @Alizter)

[mbarbin]

I just had a first look at the CI results. This release contains ocaml-dune/pp#17 which has a breaking change to the public APi of pp. In particular Pp.to_ast no longer returns a result type. This is causing a good number of the build issues I see in the CI.

I think the normal way of fixing this is to introduce a new version constraints to these packages (& < 2.0.0 ). Is that right?

[mbarbin]

cc @rgrinberg

[mseri]

Thanks.

@mbarbin would it be possible to move 745b16a to a separate PR? This way I can directly merge and we can re-run the tests here. Otherwise the revdeps will hit heavily the CI

[mseri]

pp revdeps are all green, the builds are green. I am merging to avoid testing all revdeps of dune multiple times

[mbarbin]

Thank you!