Can this be fixed somehow, It will save some "git revert" efforts. about npm

[gr2m]

I don’t understand why you open another issue if #4 is still open. Feel free to investigate how to resolve the problem, I think Pierre made some suggestions. Pull requests welcome :)

[travi]

ive run into similar situations for unrelated reasons. outside of a change to semantic-release, i've found it simple enough to simply delete the git tag after resolving the npm issues and just re-running the build

[nozelrosario]

Yes, deleting the tag + reverting the version increment commit + re-run the release build command works, but i just need to save that extra effort.

[travi]

reverting the version increment commit

it wasn't clear from your post above what revert effort you were running into. by default, semantic-release only adds the tag. without extra commits being added to the repository, i havent had a need to do any reverting beyond the tag removal. since youve configured the version bump additionally, my suggestion doesnt fit your case quite as well