7.0.2 (2017-08-16)
Bug Fixes
-
post: create
v1.2.3tag tag instead of branch (3f85597)Note that if a version was released with v7.0.1, you will run into the
ENOTINHISTORYerror :( To recover, follow these steps:- Make sure you are on your main branch and pulled the latest changes from remote
- Edit the package.json file, set
"version"to what ever should have been released. As an example, let's say the new version number would be1.2.3. Save the change - run
npm publishto release the new version. Make sure to run any pre-publish tasks first if you have any - revert the changes
- create a tag with
git tag v1.2.3(put in the same version as in step 2. Push the tag to GitHub withgit push --tags - Manually create a release for the tag
This will fix the problem and everything will work automagically again from here on now.