Indeed, it may fail if an ADT changes in lutils or rdbg-plugin, since
this repo can only be updated if the whole pipeline succeeds (to be
able te get the release number). The idea is to rerun this job manually
when it is the case.

Rationale: a step to make time traveling work correctly.

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.

Conflicts:
	arduino/led_puzlle/arduino_puzzle.lus

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

Merge remote-tracking branch 'origin/6-can-not-iterate-over-the-plus-node-as-long-as-it-is-named-plus'

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

update the Arduino demo