[new release] merlin and merlin-lib v4.15-414/501

[voodoos]

CHANGES:

Fri May 31 14:02:42 CEST 2024

• merlin binary
  • destruct: Removal of residual patterns (destruct: Removal of residual patterns fix #1560 merlin#1737, fixes Destruct shouldn't produce same patterns in an existing pattern-match merlin#1560)
  • Do not erase fields' names when destructing punned record fields (destruct: destructing punned record field breaks syntax merlin#1734,
    fixes Destructing punned record field breaks syntax merlin#1661)
  • Ignore SIGPIPE in the Merlin server process (Ignore SIGPIPE in the Merlin server process merlin#1746)
  • Fix lexing of quoted strings in comments (Test and fix wrong error with string literal in comment merlin#1754, fixes string litteral with an extension node is wrongly marked as being unterminated merlin#1753)
  • Improve cursor position detection in longidents (Improve context detection for infix operators merlin#1756)

[mseri]

Seems like none of the merlin is installable, e.g.

merlin.4.15-414 is not installed. Install it? [y/n] y
  * No agreement on the version of merlin-lib:
    - merlin = 4.15-414 -> dot-merlin-reader >= 4.9 -> merlin-lib < 4.14-502
    - merlin = 4.15-414 -> merlin-lib = 4.15-414
  * No agreement on the version of ocaml:
    - (invariant) -> ocaml-base-compiler = 4.14.2 -> ocaml = 4.14.2
    - merlin = 4.15-414 -> dot-merlin-reader >= 4.9 -> ocaml >= 5.2
    You can temporarily relax the switch invariant with `--update-invariant'

[voodoos]

With the final release of Merlin for 5.2 I decided to bump the major version number due to the large number of apj changes.
I moved the constraint to be merlin-lib < 5.0, which should hold for some time since we are only going to do maintenance releases for older versions of the compiler.

I am wondering whether we should move to always releasing dot-merlin-reader along with merlin/merlin-lib either if there is no changes at all to simplify the version contraints ?

@mseri I surprised that the CI turned green with one of the two packages released actually being un-installable 😅

[mseri]

Thanks. Now it looks all right.

@mseri I surprised that the CI turned green with one of the two packages released actually being un-installable 😅

Failing to satisfy the constraints is a "SKIP [Package not available]" warning since there are a massive amount of packages that are uninstallable in certain configurations by design. It is for us to check that it looks all right in the fully unistallable cases, but probably a lint could be added for this