StoneCypher / jssm / b0681f049856285bd3129f539f601a3e8bec758f / 7

100%

master: 100%

push

github

ci(release): make release-create and npm-publish idempotent

Prior runs that failed mid-pipeline (e.g. at npm publish after the
release object was created) blocked all subsequent re-runs because
`gh release create` 422s on an existing tag and `npm publish` errors
on an already-published version. Switch both steps to
check-then-create-or-update: `gh release view` gates create vs edit,
and `npm view <pkg>@<ver>` gates publish vs skip. Re-running a
partially-failed release pipeline now resumes cleanly from wherever
it last stopped.

827 of 827 branches covered (100.0%)

Branch coverage included in aggregate %.

7599 of 7599 relevant lines covered (100.0%)

849.89 hits per line