semantic-release setup

[gr2m]

see

• Proposal for adding semantic-release to Hubot 🤖  evolution#6
• https://github.com/hubotio/evolution/blob/4/javascript/_drafts/javascript.md#publish-hubot300-with---tagnext

for a release to happen, we have to add another commit which can be done using --allow-empty. hubot@3 comes with a new feature and 3 breaking changes. The commit can look as follows:

feat: `require('hubot/es2015')` exports native ECMAScript 2015 classes

BREAKING CHANGE: node@0.10 and node@0.12 are no longer supported
BREAKING CHANGE: Deep requires like `require('hubot/src/adapter')` are no longer supported, use `require('hubot').Adapter` instead.
BREAKING CHANGE: `Middleware.ticker()` has been removed. Use `process.nextTick()` instead.

[gr2m]

the test with Node 4 fails because npm errors if peerDependencies are not fulfilled while npm 3+ only shows a warning. I suggest we add 0.0.0-development as a valid peerDependency, so the full value would be

  "peerDependencies": {
    "hubot": ">=2 <10 || 0.0.0-development"
  },

I tested it locally and it worked. I’ll update the evolution process and the PRs that I already sent to the scripts

[technicalpickles]

Was it intentional to remove the CHANGELOG.md? Should we keep that around for things before semantic-release is used?

[gr2m]

@technicalpickles we will add a link to the last version of the CHANGELOG.md file on the 3.0.0 release notes

[gr2m]

@technicalpickles alternatively we could create releases for past versions and put the changes in each release note, would you like me to do that?