I'm not quite sure if I understand your question completely. The tool should not be used to trigger a CI pipeline. The idea behind node-publisher was to prevent broken packages being published. A CI helps us in the…
Releasing a new version of a package usually happens from the developer's terminal and it's a manual process, prone to human error. The tool just automates what otherwise would be done manually.
I'm not quite sure if I understand your question completely. The tool should not be used to trigger a CI pipeline. The idea behind node-publisher was to prevent broken packages being published. A CI helps us in the…
Releasing a new version of a package usually happens from the developer's terminal and it's a manual process, prone to human error. The tool just automates what otherwise would be done manually.