add auto-release

[tharvik]

tried out releasing v2.2.0 & v2.2.1 and it seems to be working.

• container image published with tag 2.2.0 & 2.2.1, "develop" image is now called edge
• npm packages have two new version 2.2.0 & 2.2.1
• we can easily write a new relase based on theses tag

so when pushing a commit and tag with npm version bumps for main packages, it works. we can release v3.0.0 anytime.

[JulienVig]

Nice!
Is it triggered by merging a commit message like "v3.0.0" into the develop branch? Is there an exact format to follow?
Could you add the details of the publishing process somewhere in the doc?

[tharvik]

Is it triggered by merging a commit message like "v3.0.0" into the develop branch? Is there an exact format to follow?

it is using git tag to know which commit is to be released. with our CI, it needs to have the v$version format to be picked up (it's quite used all around).

Could you add the details of the publishing process somewhere in the doc?

good idea, I rewrote the docs' deployement file to explain the process in more depth.