https://www.npmjs.com/package/semantic-release-gitlab

from https://semver.org/ :
  Given a version number MAJOR.MINOR.PATCH, increment the:

  - MAJOR version when you make incompatible API changes,
  - MINOR version when you add functionality in a backwards-compatible manner, and
  - PATCH version when you make backwards-compatible bug fixes.

For MAJOR, choosing 6 is obvious.

From Minor it's not clear. This number is supposed to reflect the number of
add functuionnality, so starting at 0 is not great.

The current version is 1.762, but starting at 762 would be wrong too,
as most do not deals with new functionnalyties.

In a ideal word, I should use the log and tag every commit tha deals with a new
functionnalyty, but there is a lot of commits (762).

Hence I,'ve decided to choose 100.

update the Arduino demo

The generated code for tests on boolean output was wrong. Indeed, it
was generating

  if (o1 == _true) {

instead of

  if (*o1 == _true) {

nb : a warning was emited

Add code to support empty arrays (not yet working)

It was generetaing wrong code in conjunction with -ec.

In particular, it was generating n-any "and" instead of binary "and".

Also, I needed (in L2LExpandEnum) to generated a Lic.ARRAY of const
instead of a Lic.Array_const_eff so that LicDump properly generated
ec code.

which was not even compiling...

More precisely, transforms equations of the form

   y = x when Toto(c);

into

   x when Toto_c ;
   Toto_c=Toto(c);

Also, force a workflow (via a lock file named commited) that make
sure that the content of lv6version.ml is always correct xrt shat and
git commit number.