Better CI and release process about js-sdk HOT 4 CLOSED

I can do it ^^
I already started on the related issue

from js-sdk.

My guess is there's 2 options here :

1. abide by commit messages convention and get everything automated (using for example commitlint and semantic-release libraries), but that implies that commit messages will have to be carefully written
2. get more flexibility but less automation by git tagging manually each release, have the CI to parse the tag name and deduct which files to upload to GitHub Release

As of the current state of the project by now I would recommend going for the second approach before considering full automation in the future.

from js-sdk.

It seems that lerna has a command lerna version that creates and publishes the tags without publishing on npm. We could use that and then have a standard deploy on npm when there is a new tag. That would follow your second proposition.
Just something to keep in mind (even it shouldn't be a problem), we will have multiple packages in this repository so multiple tags for the different libraries. You can check the existing tags https://github.com/mesg-foundation/js-sdk/releases

from js-sdk.

Issue migrated to liteflow-labs/liteflow-js#20

from js-sdk.