Release Strategy

The master branch automatically creates release for the next dist-tag.

The latest dist-tag has to be moved manually. Run npm dist-tag add eslint-plugin-meteor@<version> latest.

This strategy means the next dist-tag will spit out updates with every relevant commit to master resulting in many small releases. When a specific release is tested and accepted as good, the latest tag can be moved to it manually.

Having release candidates is not necesssary when using semantic releases:

"With semantic-release it’s discouraged to put information about stability into the version number (i.e. 1.0.0-beta or 2.0.0-rc1) because it’s mixing things up. The tool you can use to comunicate stability are npm’s dist-tags. The last paragraph of this section should give you some hints: https://github.com/semantic-release/semantic-release#how-does-it-work"

boennemann, source