Automatic publication of the NodeJS package

[teolemon]

No description provided.

[PieterT2000]

@teolemon I can create a PR for this if nobody else is already working on this? Please let me know when you can.

[teolemon]

@PieterT2000 yes, of course, that would be great 👍

[PieterT2000]

Wow, that was fast!

Could you explain the typical release procedure (including branch strategy/Gitflow) or link some info in here? I assume that apart from breaking change releases you also do minor and patch releases?

I can see that there is already a Github action that seems to be handling automated NPM publishing, but it has never been run. (See here) Is this because there hasn't been an official Github release yet?
Moreover, #323 mentions about creating alpha and beta NPM releases. Is this still relevant? If yes, would it be an idea to create a beta branch? The new release strategy would then become: release branch -> beta -> develop. Additionally, an alpha release will be created whenever the first release PR is opened on the release-please--branches--* branch.
Alternatively, we can also do just beta releases whenever a release PR is opened, getting rid of the intermediary beta branch. This approach keeps your existing branch strategy.