setup CI for publish

[sivukhin]

Setup CI for automatic publish of NPM package based on the tag:

• Tags matching v* pattern with -pre substring will be published as pre-release versions (npm publish --tag next)
• All other tags matching v* pattern will be published as latest package version (npm publish)

[notrab]

If we want to go down the path of setting up a monorepo then using chanegsets in the CI for publishing would be an easier route. That way we can handle semver much easier, and roll multiple merges into single releases.

Changesets seems to be a common standard these days. Here’s an example of how I have it setup on another project.

[sivukhin]

@notrab - for now I want at least to have ability to publish packages without @penberg
We can change it any time to use changeset - but I want to merge this for now