Publishing new version

1. Make sure npm test and npm run lint are passing without errors.
2. Make sure all new features and APIs introduced in the release are documented.
3. Increment version in package.json
4. Add entry in CHANGELOG.md. Header of the entry should have format ## VERSION.NUMBER - YEAR-MONTH-DAY. Each entry must be credited with github username of the patch author. Entries must be sorted in order:
   1. Potentially breaking changes
   2. New features
   3. Bugfixes
   4. Other changes
5. Commit the changes and tag the release. Use annotated git tags (git tag -a).
6. Push the changes and the tag into the repo and wait for TravisCI build to finish. npm package will be published automatically, there is no need to call npm publish.
7. Copy changelog entry to the Releases page.