Setup semantic-release

[limonte]

Closes our emotional discussion in #242 (comment) :)

You're already using Angular Commit Message Conventions for this repo, so setting up semantic-release is simple, read more: https://github.com/semantic-release/semantic-release/

In order to publish to GitHub, add GH_TOKEN or GITHUB_TOKEN env variable in Travis config, read more: https://github.com/semantic-release/github/#environment-variables

In order to publish to npm, add NPM_TOKEN env variable in Travis config, read more: https://github.com/semantic-release/npm#environment-variables

That should be it.

[limonte]

One detail to finish here, the after_success task should run only once. Currently, it's being triggered for every node_js version.

Resolved.

[johnjbarton]

Thanks! Let's give this a try. If it works well we can use it on other karma-runner/*

[limonte]

Thanks! Let's give this a try. If it works well we can use it on other karma-runner/*

You're welcome! Sure, you can apply the same config for other repos. As you can see, the configuration is quite simple.

[limonte]

The releasing process failed because env variables aren't set, add GH_TOKEN and NPM_TOKEN to Travis and re-run the build, then the releasing magic should happen.

[johnjbarton]

Like #249 ?

[limonte]

Like #249 ?

No. You just exposed your sensitive data, you need to delete those tokens ASAP! Otherwise, someone will use them for evil purposes.

[limonte]

The right way is described here: https://docs.travis-ci.com/user/environment-variables/#defining-variables-in-repository-settings

[johnjbarton]

Thanks, but our travis acct has no repo settings. I'll have to dig in to that.

[karmarunnerbot]

🎉 This PR is included in version 3.1.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[johnjbarton]

ok eventually I got all the things to work. Thanks!