Make release script more robust

[timaschew]

Bug Report

Steps to reproduce

RELEASE_TAG=next ./build/release.sh

What is current behaviour

docsify-server-renderer was published to npm
but not docsify nor it was pushed to github

What is the expected behaviour

check all packages before publishing
check repository (if fast-forward is possible) before pushing to github or publishing to np,
either all packages should be published/pushed to github or nothing should published/pushed

Other relevant information

• Bug does still occur when all/other plugins are disabled?

• Your OS:

• Node.js version:

• npm/yarn version:

• Browser version:

• Docsify version:

• Docsify plugins:

[jrappen]

It might help rolling back to the previous use of a mono-repo for development for all repos of the https://github.com/docsifyjs organisation. I found the the creation of separate repos for translations and the cli not helpful with trying to coordinate development of all things docsify related ... but maybe it's me.

Having a look at https://github.com/vuejs/vuepress/blob/master/scripts/release.js might help with the release script here.

[anikethsaha]

I am +1 for making the release script in more depth.

I was thinking about standard-release but that might change the changelog.

Having a look at https://github.com/vuejs/vuepress/blob/master/scripts/release.js might help with the release script here.

This looks interesting. Maybe we can have this.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.