Automate canary releases to npm

[johno]

As @ChristopherBiscardi mentioned we should begin automating canary releases to npm. We can follow the flow similarly to next and gatsby-mdx via Travis CI.

[ChristopherBiscardi]

Seems like a good first issue for someone. Main task is to add the script mentioned in the comment above, and have it execute only if the travis build is master branch and everything else has passed.

[timneutkens]

This will probably help: https://github.com/zeit/now-builders/blob/master/.circleci/config.yml

[leimonio]

This PR #376 has also failed because of npm authentication on Travis CI.

[johno]

I set an NPM_AUTH_TOKEN as an env var. I was under the impression that would be picked up for npm authentication but I guess I'm mistaken?

[leimonio]

It doesn't seem to properly getting deployed, just checked the latest build and fail for the same reason. I've opened another PR for properly setting .npmrc file on Travis. #393

[johno]

I've updated the token env var to be NPM_TOKEN. Hopefully that does the trick.

[johno]

Looks like this is almost working! Looks like the way the ci versions are being generated makes is causing issues.

[leimonio]

I've added another script to explicitly fetch tags before publishing #400 We're almost there! 🤞

[johno]

Looks like we're now g2g, thanks @leimonio!

[leimonio]

@johno That's great, glad I helped! Let me know if I can help to migrate current CI/CD configuration to circleci.

[johno]

If you wanted to take that on, feel free to write up an issue and assign yourself. That would be greatly appreciated!