Question: How to proceed if NPM publish fails about semver HOT 2 OPEN

Hi, to avoid pushing tags and version commits if NPM publish fails you could do this:

• set --push to false as the push occurs before post-targets
• write a custom post-target "git-push" that pushes the new version
• declare the "git-push" target next to the NPM publish so it's not executed if the publish fails

So it could look like:

"targets": {
  "version": {
    "executor": "@jscutlery/semver:version",
    "options": {
      "postTargets": ["npm-publish", "git-push", "github-release"]
    }
  },
  "npm-publish": {
    "executor": "ngx-deploy-npm:deploy",
    "options": {
      "access": "public"
    }
  },
  "git-push": {
    "command": "git push --atomic --follow-tags"
  },
  "github-release": {
    "executor": "@jscutlery/semver:github",
    "options": {
      "tag": "{tag}",
      "notes": "{notes}"
    }
  }
}

from semver.

Just fyi: If you try something like above, be aware that concurrent commits to your main branch will break the above workflow. This may due to concurrent runs of your release pipeline, or something pushing directly to your main branch. You may end up with a package release to npm without release commit & tag being pushed to your main branch.

I personally find it much easier to have tested & tagged commits in git and have an additional manually-run workflow that, given a tag name, (re)publishes this tag as a package to npm in case a previous publish failed.

from semver.