Deploy to npm on release branch

[mattdell]

What's this PR do?

It should automatically deploy to NPM when we merge to a release branch (to be created).

I followed these instructions: https://docs.travis-ci.com/user/deployment/npm/

Where should the reviewer start?

• travis.yml

How should this be manually tested?

Well, either...

• Change the branch name to this branch to see if it works
• Merge to master, then merge master to release to see if it works

Any preference?

What are the relevant tickets / issues?

#40

[mattdell]

The variables have been added...

[vitkon]

I think we can prepare releases on a release branch but then merge it to master which will trigger a deployment.
Also, there has to be a process in place to bump the versions up, otherwise it will fail to deploy.

[coveralls]

Coverage remained the same at 84.8% when pulling 984ec10 on issue/40-use-release-branch-deploy-npm into ab56537 on master.

[codecov-io]

Codecov Report

Merging #41 into master will increase coverage by 1.55%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #41      +/-   ##
==========================================
+ Coverage   84.61%   86.17%   +1.55%     
==========================================
  Files           4        4              
  Lines          91       94       +3     
  Branches       16       17       +1     
==========================================
+ Hits           77       81       +4     
  Misses          8        8              
+ Partials        6        5       -1

Impacted Files	Coverage Δ
src/validators.ts	100% <0%> (+11.11%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ab56537...984ec10. Read the comment docs.