npm semantic-release 7.0.2
v7.0.2

latest releases: 25.0.2, 25.0.1, 25.0.1-beta.3...
8 years ago

7.0.2 (2017-08-16)

Bug Fixes

  • post: create v1.2.3 tag tag instead of branch (3f85597)

    Note that if a version was released with v7.0.1, you will run into the ENOTINHISTORY error :( To recover, follow these steps:

    1. Make sure you are on your main branch and pulled the latest changes from remote
    2. 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 be 1.2.3. Save the change
    3. run npm publish to release the new version. Make sure to run any pre-publish tasks first if you have any
    4. revert the changes
    5. create a tag with git tag v1.2.3 (put in the same version as in step 2. Push the tag to GitHub with git push --tags
    6. Manually create a release for the tag

    This will fix the problem and everything will work automagically again from here on now.

Don't miss a new semantic-release release

NewReleases is sending notifications on new releases.