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.

It causes bad error messages in the case were the parametric node is undefined.

e.g., the equation

  S=if(M[n-1]) then (entiernat<<n>>(M)-puiss<<n+1>>(2)) else entiernat<<n>>(M);

raises "Error: Bad number of (static) arguments: 0 expected, and 1 provided."
when entiernat is undefined

It seems useless because no test is broken. The comment mention node
parameters that themselves have parameters. But it is the case for
test/should_work/Gyroscope2.lus, and it is still working.

update the Arduino demo

nb: i should really add 'make test' in the git commit hooks!

update the Arduino demo

Remove unused files along the way (myGenlex.ml/mli)

By not catching errors, rdbg and (thus) lurette were silently do nothing
in presence of errors in Lustre files.

The idea is to be able to take into account clock in node profiles
when generating the main simulation loop, and to avoid to read inputs
that are not present.

add and install an alias to lus2lic name lv6.

lus2lic --gen-autotest now overrides existing _oracle*.lus and _env*.lut files

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)

Also, use rdbg instead of lurettetop to run the test.

also:
 -2cw7: fix the generated script
 arduino dir: minor fixes

with recursive clock depende ncies.

Reference Manual enhancements.

- add a sectiuon on operators priority
- fix the automatic latex grammar generator (now calles yacc2latex)

also force the -rif in the utils/luciole-rif script when used with
lutin or lus2lic.

Actually, that was the default behavior. Now the default behavior is
to generate loops for iterators.

nb : with -2ch, loops are still always inlined

Currently no integrity check is performed (i.e., check that each node
that uses an unsafe node is itself declared as unsafe).

Add the modes3x2 exemple of Pascal (its version + a la V6 version).

Fix the doc wrt the merge exemple (the tex was refering to a
non-existant file).

Actually, it was a misunderstanding of mine (R1) ; the behavior was consistent
with the lv6 doc, but not with the v4 behavior...

Indeed, # means "at most 1 among n", not "exactly one among n" as I tought...

nb : do not work for lv4/ec mode

'-' replaced by 'm', '.' by 'd',
(see "correct_num_string" in LicDump.ml)

maintaining (ugly and error-prone) hash tables.

That change revealed an untriggered bug in EvalClock.check_args: it was wrong
to add in subst the substitutions made of the parameters and the arguments (it
is enough to unify the clocks of the pars and of the args). For instance, consider
the node (in should_work/clock/clock.lus)

   node clock5(x :  bool; y:  bool when x; z: bool when y)

and the call

  z2 = clock5(a, b when a, c when e);

I was adding y/b in the subst, which was wrong.

Other minor changes:
 - move const_to_val_eff from Eff to UnifyClock.
 - GetEff.translate_val_exp now returns a substitution, in order to be able
   to unify clock vars and propagate the resulting substitution.