Splits publication step in 2, so package tarballs are all created first, then are all published to npm.
Useful for manual inspection between those steps, and to avoid issues where it fails halfway through with an error and is difficult to resume. Now, just delete the successfully published tarballs and try again.
New set of publish steps:
-prepareVersion: bump version, fixup changelog, wait for you to write changelog entry.
-version: create version commit, tag in git
-packageForPublishing: create all tarballs that will be published, dump in packages subdirectory for inspection, each named after its dist-tag
-publishPackages: loop through the tarballs, publishing each to npm with dist-tag parsed from filename (set in previous step)
-postPublish: Create empty changelog entry for next version, commit it, push commits and version tag
Splits publication step in 2, so package tarballs are all created first, then are all published to npm. Useful for manual inspection between those steps, and to avoid issues where it fails halfway through with an error and is difficult to resume. Now, just delete the successfully published tarballs and try again.
New set of publish steps:
-prepareVersion: bump version, fixup changelog, wait for you to write changelog entry.-version: create version commit, tag in git-packageForPublishing: create all tarballs that will be published, dump in packages subdirectory for inspection, each named after its dist-tag-publishPackages: loop through the tarballs, publishing each to npm with dist-tag parsed from filename (set in previous step)-postPublish: Create empty changelog entry for next version, commit it, push commits and version tag