title: Generate changelog for a semantically released package
body: <p>Here is <a href="https://github.com/alecxe/eslint-plugin-protractor" rel="noreferrer">the package</a> I'm working on currently.</p>
  
  <p>This is the first time I'm trying to enforce the <a href="https://github.com/ajoslin/conventional-changelog" rel="noreferrer">conventional changelog</a> format and use <a href="https://github.com/semantic-release/semantic-release" rel="noreferrer">semantic release versioning</a>. The releasing itself works fine, I'm having travis CI testing, building and publishing the package to npm, creating a new version and a git tag. There is also a <a href="https://github.com/blog/1547-release-your-software" rel="noreferrer">GitHub package release</a> created, which is, in a way, a replacement for a separate changelog file.</p>
  
  <p>What I'm trying to achieve next is to <em>automatically generate the ChangeLog based on the latest release changes</em>. From what I understand <code>conventional-changelog</code> can help with that, but whenever I run:</p>
  
  <pre><code>$ conventional-changelog -p eslint-plugin-protractor -i CHANGELOG.md -w -r 0
  </code></pre>
  
  <p>I'm getting all the changes grouped under the <code>0.0.0-semantically-released</code> version, which is the stub <code>version</code> I put into the <code>package.json</code> to avoid warnings during <code>npm install</code>.</p>
  
  <p>What am I doing wrong and how can I generate logs for every semantic release version? </p>