fix(package): update @semantic-release/last-release-npm to version 2.0.0

https://greenkeeper.io/

README.md

@@ -106,7 +106,7 @@ format that includes a **type**, a **scope** and a **subject** ([full explanatio
 <footer>
 ```
 
-You can simplify using this convention for yourself and contributors by using [commitizen](https://github.com/commitizen/cz-cli) and [validate-commit-msg](https://github.com/kentcdodds/validate-commit-msg) or [semantic-git-commit-cli](https://github.com/JPeer264/node-semantic-git-commit-cli).
+You can simplify using this convention for yourself and contributors by using [commitizen](https://github.com/commitizen/cz-cli) and [commitlint](https://github.com/marionebl/commitlint) or [semantic-git-commit-cli](https://github.com/JPeer264/node-semantic-git-commit-cli).
 
 ### Patch Release
 

TROUBLESHOOTING.md

@@ -0,0 +1,34 @@
+# Troubleshooting semantic-release
+
+### ENOTINHISTORY Commit not in history
+
+```
+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 "123".
+semantic-release ERR! pre Failed to determine new version.
+semantic-release ERR! pre ENOTINHISTORY Commit not in history
+```
+
+To restore semantic-release, follow these steps:
+
+```
+git pull
+git reset --hard origin/master
+npm version x.y.z # check your current version and set this based on semver rules manually
+
+# if you have a PR workflow, create a new branch, otherwise commit to master
+
+git checkout -B chore/release
+git commit -am 'chore: release'
+git push
+
+# merge (not squash-merge) on github (this is important before running git push). This is only required when you work with branches
+git checkout master
+
+# definitely required
+git pull
+git push --tags
+npm publish
+```

package.json

@@ -9,15 +9,17 @@
   "bugs": {
     "url": "https://github.com/semantic-release/semantic-release/issues"
   },
-  "czConfig": {
-    "path": "node_modules/cz-conventional-changelog/"
+  "config": {
+    "commitizen": {
+      "path": "cz-conventional-changelog"
+    }
   },
   "dependencies": {
-    "@semantic-release/commit-analyzer": "^2.0.0",
+    "@semantic-release/commit-analyzer": "^3.0.1",
     "@semantic-release/condition-travis": "^6.0.0",
     "@semantic-release/error": "^1.0.0",
-    "@semantic-release/last-release-npm": "^1.2.1",
-    "@semantic-release/release-notes-generator": "^3.0.1",
+    "@semantic-release/last-release-npm": "^2.0.0",
+    "@semantic-release/release-notes-generator": "^4.0.0",
     "git-head": "^1.2.1",
     "github": "^8.0.0",
     "lodash": "^4.0.0",
@@ -34,7 +36,7 @@
   },
   "devDependencies": {
     "coveralls": "^2.11.4",
-    "cz-conventional-changelog": "^1.1.4",
+    "cz-conventional-changelog": "^2.0.0",
     "mkdirp": "^0.5.1",
     "mock-spawn": "^0.2.6",
     "nixt": "^0.5.0",