simon/semantic-release
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs(troubleshooting): initial version (#399)

Browse Source
This commit is contained in:
Patrick Heneise 2017-09-13 21:10:50 +02:00 committed by Gregor Martynus
parent 12b35396d8
commit 1ceae83ad9
1 changed files with 34 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

34
TROUBLESHOOTING.md Normal file
View File

@ -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
```