Problem with semantic release from Travis

```
> semantic-release pre && npm publish && semantic-release post
[travis-after-all] Job succeeded (d63814a9f0608780342d504d17c98b81d7a07badfefc08839edbaf49d1dacbdb)
semantic-release ERR! commits The commit the last release of this package was derived from is not in the direct history of the "master" branch.
semantic-release ERR! commits This means semantic-release can not extract the commits between now and then.
semantic-release ERR! commits This is usually caused by force pushing, releasing from an unrelated branch, or using an already existing package name.
semantic-release ERR! commits You can recover from this error by publishing manually or restoring the commit "983daf4827399a19ed85742927c0bf3775c47d5d".
semantic-release ERR! pre Failed to determine new version.
semantic-release ERR! pre ENOTINHISTORY Commit not in history
```

Start with the Travis release command `semantic-release pre && npm publish && semantic-release post` and inspect the repository history for commits `983daf4827399a19ed85742927c0bf3775c47d5d` and `d63814a9f0608780342d504d17c98b81d7a07badfefc08839edbaf49d1dacbdb`. Determine why the release commit is absent from master and document or implement a reliable recovery path so semantic-release can complete.

Written by the indexing model from the issue text.