A better rollback when something fails

[mgol]

If anything throws in a process before we publish on npm, a full rollback should happen (including a push --force on a branch to the previous version?)

[agonbina]

Hey @mgol, it would definitely be nice to rollback when something fails.

[mgol]

Hmm, it should be enough to wrap

npm-bump/lib/cli.js

Lines 86 to 89 in e665175

	run(`git checkout ${ quote(newStableVersion) } 2>/dev/null`);
	run(`npm publish ${ quote(getRootPath()) }${
	isPrerelease ? ` --tag ${ quote(releaseType) }` : '' }`
	);

in try-catch and do the rollback on error. Wrapping more things would be problematic as it npm publish succeeded and next Git operations failed we can't revert the npm publish (we could unpublish but you can't then re-publish the same version).

Thoughts? Would you like to prepare a PR?

[mgol]

Or maybe `npm publish` should be moved to be the last operation so that we always can fully rollback unless we finish all remote operations.

[aj-dev]

@mgol I agree, npm publish should definitely be the last thing we do.