Setup automated build / release process using GitHub actions and Chan…

[JakeGinnivan]

trafficstars

…gesets

I removed the travis.yml as GitHub actions will do the build/release for you.

How changesets works

When anyone is submitting a PR, run npm run changesets, the wizard asks what semver and a description of the change. It creates a temporary file with the change info.

When this PR merges, the GitHub release action will run, which will open a pull request with a changelog of the unreleased features. As PRs merge this PR will get automatically updated with all unreleased changes. When that PR is merged, it will publish the new beta to NPM.

When you want to release the next version you can run npm changesets pre exit which will allow you to bump minor and go to 0.3 or whatever you want. Docs are pretty good.

What you need to do

Add a NPM_TOKEN to your project secrets which will be used to push to NPM before you merge the second PR.

You can merge this PR, see changesets open the release PR then add the NPM_TOKEN after it opens so you can see how it works before allowing it to push to NPM.

Fixes #35

[jeremydaly]

I haven't forgotten about this! Will look again after we have the TS version out there.

[jeremydaly]

I just released v0.3.0. I'm going to take a look at incorporating this. Thanks again!