Setup releases

[nlopin]

Context

We release by publishing builds in the release branch. Every merge triggers build which creates a new commit in the release branch. Than the consumer picks the update by the commit hash:

"@factorialco/factorial-one": "github:factorialco/factorial-one#07bdd7fc04e3b9dcc93e672087b076be5cba1df3"

The solution is simple and serves us well.

Problem

• The only release branch makes it impossible to have experimental builds or prepare major changes because the releases go in sequence and there is no way to branch it.
• We have no way to communicate to users about the scale of the change. All versions look the same and the only way to understand the change is to review the changes in the commit

Solution

I don't have a strong opinion on what to do here, but the most obvious approach would be to release the library in the NPM Registry, which will unblock the regular library development flow.

The second option is to have an experimental release branch with manual release process. This will add some work and knowledge to share.