ed89361d7c
**Refactor and clarify the documentation in `README.md`** - Add Highlights - Add a Table of contents - Clarify the way semantic-release works - Clarify relationship with the CI environments - Describe local install for Node projects (with a `package.json`) and global install for non-JavaScript projects - Explain CI general configuration (environment variables and a run after all jobs are successful) - Clarify configuration (via config file or CLI arguments) - Clarify plugin roles and configuration - Add doc for shareable configuration - Add recipes - Add resources (Videos, articles, tutorials) - Add a Support section - Add a Team section **Add the following FAQs** - How can I use a npm build script that requires the `package.json`’s version ? - Can I use Semantic-release with Yarn? - Can I use Semantic-release to publish non-JavaScript packages? - Can I use Semantic-release with any CI service? - Can I use Semantic-release with any GitLab? - Can I use Semantic-release with any Git hosted environment? - Can I skip the release to the npm registry? - Can I use .npmrc options? - How can I set the access level of the published npm package? - Can I use Semantic-release to publish a package on Artifactory? - Can I set the initial release version of my package to 0.0.1? - Why does semantic-release require Node version >= 8? **Clarify Nove 8 requirement and solutions** - Add Node version requirement explanation and solutions - [X] Display a link to the documentation when running on Node < 8 version **Add recipes** - Travis - GitLab CI - Travis with build stages - To be done in #573 - CircleCI workflows - To be done in #573
35 lines
1.2 KiB
Markdown
35 lines
1.2 KiB
Markdown
# 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
|
|
```
|