Publish to npm on each commit in master

[evidolob]

This PR add GH Action workflow which publish changes in master branch to npm registry with next version tag.

[coveralls]

Coverage remained the same at 77.923% when pulling 441effb on publish-next-versions into 3742beb on master.

[joshuawilson]

If you merge this you will have 2 workflow files that will both fire when merge to master is detected. They do not have a dependency so failing the test will not keep it from releasing.
You will either need to find a way to chain them. (after a quick search I do not see how to do that)
OR you will have to put everything in one workflow file and use conditionals there. (not sure this will work either)

[evidolob]

@joshuawilson nice catch.
We can run tests in CD workflow or I can move everything in to one workflow

[joshuawilson]

You could have one for on push to master and another for on PR. Both run the tests but only one will release.

[JPinkney]

Yeah good catch, I completely forgot about that

[joshuawilson]

Chaining would be cleaner as it would not duplicate the test and build steps but I can not find a way to do it.

[evidolob]

OK, I think I know how to do that, I will update PR soon, all steps will be in one workflow

[joshuawilson]

How do you ensure that the other workflow runs first?

[evidolob]

Which one? We have only one workflow.

[joshuawilson]

Sorry, I thought this was an update to the CD workflow. I missed that are only using one now.
This is a nice solution, good work.