Use a github action workflow to release new versions

[QuentinLemCode]

Hello

Following the empty 5.3.0 version on NPM, I suggest to use an automated workflow to avoid this in the future.

This PR add a github action workflow to perform automated releases.

The release workflow can only be launched manually with a choice for the type of release (major, minor, patch).
You can add a release message.

Required : Add the NPM authentication token inside repository secrets with the name NPM_AUTH_TOKEN

[TheAlan404]

is a .npmignore also needed here?

[QuentinLemCode]

is a .npmignore also needed here?

Yes I add it

[alumni]

@jaredwray could you please review this? thanks!

[QuentinLemCode]

We also need to add the package-lock because npm install will create the file and make npm version fail because of pending changes.

[jaredwray]

@QuentinLemCode - thanks for the update on this and we might want to get something a bit more simple where we arent doing the version bump in the code. Either way, I can do an update on that after the merge.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (af72f55) 100.00% compared to head (ef3fa10) 100.00%.

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

@@            Coverage Diff            @@
##            master      #612   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            5         5           
  Lines          295       295           
  Branches        76        76           
=========================================
  Hits           295       295           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[QuentinLemCode]

@QuentinLemCode - thanks for the update on this and we might want to get something a bit more simple where we arent doing the version bump in the code. Either way, I can do an update on that after the merge.

@jaredwray You are welcome
Yes we can do that and trigger the publish on a new release
Don't hesitate to comment the review, I will be happy to help

[guslen]

Hi @QuentinLemCode,
I had a similar idea, but I used semantic release. Feel free to copy paste from there #613

[jaredwray]

@QuentinLemCode thanks so much for the work on this.

@guslen - I will be doing some tweaks to this to simplify it down but if you have any suggestions let me know and feel free to create an issue to dialogue about it first.